Skip to main content

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

Robot activity chart

Updated on November 29, 2022

The Robot activity chart provides a graphical breakdown of robot performance in a work group on a specific date. Learn how to read the chart by analyzing a sample use case.

As a robot administrator, use the data provided to better understand how your robots are used across the day.

For example, if robots spend more time requesting new assignments than working, this might indicate that you need fewer robots to efficiently process the work.

The sample use case here is the following snapshot of robot activity in a work group:

Robot activity in a work group
Robot activity in a work group by individual robot, with their status, along a timeline of their operation.
Note: This snapshot provides a graphical representation of a specific use case that might not be replicable on your system.

The column on the left of the timeline lists the robots in the work group, and the colored activity bars on the right indicate the sessions during the day that the robot worked within the work group. The icon preceding each activity bar indicates how the robot was started. Use the left mouse button to move through the timeline. Using the mouse scroll wheel zooms the timeline in and out. For more information about a robot's status and startup indicators, click the Help gadget in the top-right corner of the chart.

The following description provides a breakdown of the robot activity in the work group depicted in the sample use case:

  1. Pega Robot Manager™ automatically starts a robot in the Account management work group because new assignments were created and no robots that could perform the work are active in that work group.
  2. An additional robot starts completing assignments, based on an existing schedule.
  3. Because two robots are now working on assignments, Robot Manager calculates that a single robot is enough to complete the remaining work within the SLA boundaries and stops the robot that was started by the auto-balancing engine.
  4. Robot Manager restarts the robot that it previously stopped because of a new batch of open assignments that requires more than one robot to efficiently process the assignments.
  5. Half an hour later, Robot Manager starts the third robot in the work group, because the number of open assignments is increasing.
  6. A new robot starts completing assignments in the work group as a result of a scheduled start. The four robots continue working in the Account management work group, in an effort to complete all assignments on time.
  7. Because the number of open assignments is decreasing, Robot Manager determines that the scheduled robots alone can complete all the remaining work efficiently, and stops the two robots that were assigned to the work group through automatic workload balancing.
  8. The two scheduled robots continue completing the remaining work until there are no queued assignments. The scheduled robots have no work assignments, enter the Ready state and poll for work.
  9. New open assignments are created and the scheduled robots start working again.
  10. A new robot starts working in the work group. That robot does not request for work. Instead, that robot runs an automation immediately after deploying the package.

Tip: To supplement work group-specific activity data, you can analyze the activity of a single robot across multiple work groups, as shown in the following example, in which each work group is represented by a distinct color:
An activity breakdown of a single robot
An activity breakdown of a single robot, using the same timeline and icon arrangement as the group view.
For more information, see Monitoring work groups.

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