Skip to main content

Robot intervals and thresholds

When configuring unattended robots in Pega Robot Manager, you can keep your robots performing optimally by adjusting the frequency with which various events occur in relation to robot performance and health. For example, you can specify the frequency with which robots request work or provide their health status. You can also configure robot failure tolerances to monitor robots performing under your set threshold limits.

You configure these settings in two ways:

  • By using robot intervals, which apply to all robots
  • By using work group intervals and thresholds that apply to a specific work group

Robot intervals

Robot intervals provide a method of keeping your robots under control and functioning within their given Service-Level Agreement (SLA). You can set robot intervals in the Intervals section of the Configuration settings page. To change the application settings, you must have administrative privileges and an unlocked Ruleset in your current application. The following figure shows the Robot intervals settings in Robot Manager:

The Robot intervals section of the Configuration settings page in Robot Manager.

The following table describes each of the interval settings shown in the preceding figure:



RPA Service heartbeat

Determines the frequency with which the RPA Service sends the heartbeat message. The default value is 30 seconds.

Notification alert

Prevents the system from sending repeated notifications of the same type. The default value is 30 minutes.

Not ready threshold

Determines how long a robot can be in the APPLICATION NOT READY state before Pega Robot Manager stops that robot. The default value is 10 minutes.

Robot heartbeat

Determines how often robots provide their health status to Robot Manager. Each robot sends a periodic message called a heartbeat to your Robot Manager application to indicate that the robot is still running and available. The robot heartbeat interval also delivers the Stop commands, Profile command, and notifies when there is a change in settings. The default value is 30 seconds

Alert evaluation time

Indicates the period for evaluating whether a robot is in the HEALTHY, FAILING, or UNDERPERFORMING state. The default value is 60 minutes.

Underperforming robot timeout

Prevents underperforming robots from performing additional assignments within the current work group until the interval expires. The default value is 60 minutes.

Auto-balancing evaluation interval

Determines the length of time in which Pega Robot Manager evaluates the expected workload in a work group by looking at how many open assignments will reach their SLA deadlines.

Work group intervals and thresholds

Each robotic work group manages different kinds of work and has different requirements for its completion. To support this, different intervals and thresholds can be set per work group.

You edit the work polling intervals and failure thresholds for a particular work group by selecting the work group whose interval you wish to modify in Robot manager in the Unattended RPA section, on the Work groups landing page.The following figure shows the location of the work group settings in Robot Manager.

The work groups settings dialog opened and display the work group intervals and thresholds in Robot Manager.

The following table describes each of the work group settings:



Consecutive failures threshold

The number of failed assignments that the assignment type can accept for each robot within the alert evaluation time. The default value is 5. A negative value prevents robots from stopping based on consecutive failures.

Failed automations threshold

The percentage of failed assignments the assignment type can accept for each robot within the alter evaluation time. The default value is 20. A value greater than 100 prevents robots from stopping based on the failed percentage.

Work polling interval

The time in seconds before a robot requests new work after completing its current assignment. The default value is 30 seconds. A value of 0 means that robots in the work group will not request any assignments.

Caution: Enabling Robot Manager to stop underperforming robots is the most efficient solution for preserving the integrity of the cases in assignments and completing work successfully within the required Service-Level Agreements (SLAs). Only disable these settings if this meets your business needs.

Check your knowledge with the following interaction:

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice