Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Understanding robot failure thresholds

Updated on December 20, 2022

Learn about failure thresholds and other settings that specify how Pega Robot Manager determines whether robots are underperforming.

Robot failure statuses

After a robot processes an assignment, Robot Manager considers any status other than Completed or Completed with errors as a failure. Failures also include the DidNotComplete status and time-outs when the robot does not reply within the defined threshold time.

Stop work scenarios

When a robot exceeds any of the thresholds, Robot Manager considers the robot for that particular work group to be underperforming, and stops the robot. Then, depending on your configuration, one of the following scenarios occurs:

Stop work scenarios

A schedule is already enabled for the robotRobot Manager starts the robot again in accordance with the original schedule. If the situation persists, Robot Manager stops the robot again, but does not restart the robot according to the original schedule.
Auto-balancing is enabled for the work groupThe root cause of the robot's repeated failure might only apply to the current work group. For example, repeated failures could be related to issues with the local application that the work group uses. If Robot Manager considers the robot to be underperforming, it stops the robot, but can move it to other work groups.
Robots are controlled manuallyThe robot remains in Stop status until a user manually starts the robot again.

Alert evaluation time

The alert evaluation time interval is a dynamic snapshot of a specific time period that Robot Manager uses to evaluate robot performance. The default alert evaluation time is 60 minutes.

For more information, see Configuring robot intervals.

Consecutive failures threshold

This value indicates the number of consecutive failed assignments that the work group can accept for each robot. The default threshold value is 5. If a robot reaches the specified threshold, Robot Manager considers the robot to be underperforming, and stops that robot.
  • The consecutive failure total does not reset while the robot is active within the same work group. For example, consider a work group in which the consecutive failures threshold is five. The robot fails three assignments consecutively at 12 AM and there are no more assignments until 4 AM. If the robot fails the next two assignments, Robot Manager stops the robot based on the threshold.
  • The consecutive failures total resets for a robot when it moves to another work group and then moves back. Consider an example of a robot that fails three consecutive assignments in work group A, and then moves to work group B, where that robot fails three additional consecutive assignments. When moving back to work group A, the consecutive failures total for that robot is still three.
Enabling Robot Manager to stop underperforming robots is the most efficient solution for preserving the integrity of the cases in assignments and completing the work successfully within the required service-level agreements (SLAs). However, if you want to disable the consecutive failures threshold for a specific business case, you can do so. For details on configuring Robot Manager to ignore the consecutive failures threshold and also on how to set the failed automations threshold, see Configuring robot failure tolerance.

Failed automations threshold

This value indicates the percentage of assignments that each robot can fail to complete within the alert evaluation time. The default value is 20%, which means that a robot can fail two out of ten assignments in the last alert evaluation interval. If a robot exceeds the specified percent of failed automations, Robot Manager considers the robot to be underperforming and stops that robot. For more information, see Configuring robot failure tolerance.

Not ready threshold

This value indicates how long a robot can remain in the APPLICATION NOT READY state before Robot Manager considers that robot to be underperforming.

Note: When a robot reports the APPLICATION NOT READY status to Robot Manager, this indicates that the robot is active, but encountered an issue while running an automation or connecting to an application.

If a robot did not start working on any assignment before assuming the APPLICATION NOT READY state, and the robot reaches the Not ready threshold, then Robot Manager stops the robot.

If a robot starts working on an assignment, reports the APPLICATION NOT READY state, and remains in this state until it reaches the Not Ready threshold, then Robot Manager waits for a length of time that is two times the assignment’s expected execution time. After this time passes, Robot Manager pulls the assignment back from the robot, and then stops the robot.

For more information, see Configuring robot intervals.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us