Skip to main content

Understanding robot failure thresholds

Suggest edit Updated on October 7, 2021

Learn about the failure thresholds and other settings through which control how Pega Robot Manager determines whether robots are underperforming.

When a robot breaches any of the thresholds, then Robot Manager stops that robot. That robot cannot perform any further tasks in the current work group.

Underperforming robots can move between work groups, because the root cause of the robot's repeated failure might be related to the current work group, for example, to issues with the local application that the work group uses.

Alert evaluation time

The 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

Indicates the number of consecutive failed assignments 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 underperforming and stops that robot.Note:

  • The consecutive failures count does not reset when a robot stops and resumes work within the same work group. For example, consider a work group in which the consecutive failures threshold is five. If a robot fails three assignments consecutively and stops at 12 AM, then starts at 4 AM as part of the same work group and fails two more assignments, then that robot is considered underperforming.
  • The consecutive failures count does not change 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, in which that robot fails three additional consecutive assignments. When moving back to work group A, the consecutive failures count for that robot is still three.

Failed automations threshold

Indicates the percentage of assignments that can fail for each robot within the alert evaluation time. The default value is 20%, which means that a robot can fail two out of ten assignments. If a robot exceeds the specified percent of failed automations, Robot Manager considers the robot underperforming and stops that robot.

Not ready threshold

Indicates how long a robot can remain in the APPLICATION NOT READY state before Robot Manager considers that robot underperforming.Note: The APPLICATION NOT READY status indicates that the robot is active but encountered an issue, for example, 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 started working on an assignment before assuming the APPLICATION NOT READY state and the robot reaches the Not ready threshold, Robot Manager waits until the assignment on which the robot is working times out and then stops the robot.

For more information, see Configuring robot intervals.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us