Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Management of work assignment issues in Pega Robot Manager

In Pega Robot Manager, administrators and users can view and investigate issues displayed on the Issues landing page. By being able to identify and process issues, administrators can have visibility into problems and determine the best course of action for resolution.

The issues that are displayed in Robot Manager only relate to unattended robots.

Issues are accessible from the navigation pane of Robot Manager, as shown in the following figure:

Accessing the Issues landing page in Robot Manager.

Issues in automations

When a robot completes an assignment, Robot Manager receives one of the following status notifications:

  • Completed
  • DidNotComplete 
  • CompletedWithErrors

If an assignment is not successfully completed, a status of either CompletedWithErrors or DidNotComplete returns to Robot Manager, and the assignment is categorized as an issue in one of the following categories:

Issue category

Description

Automation failures

An assignment where the robot attempted to complete the assigned work. These assignments do not complete fully and return a status of CompletedWithErrors. The following are examples of possible automation failures that an automation developer can investigate:

  • The required application was unavailable.
  • Application access failure.
  • Incorrect automation timing related to application response.

Conflicts

A conflict can occur when the values that return to the automation output parameters fail validation when received by Pega Platform™. For example, Pega Platform might expect to store a number as an integer value, but the automation returned a string value. These assignments return a status of either Completed or CompletedWithErrors.

Time-outs

A robot does not complete an assignment before a certain length of time has passed. Once these assignments take two times longer to complete than the Max automation run-time setting value, they are categorized as Time-outs. For example, the cause of a timeout might be a result of the automation taking a long time to respond because of slow application activity. An error occurs while running an automation, which causes the process to exceed the Max automation run-time setting.

Unexpected errors

When an automation encounters an unhandled exception error, it prevents the robot from completing its work. If the robot cannot complete the assignment because of the error, a status of DidNotComplete returns to Robot Manager. The following list features some automation examples that can cause an unhandled exception:

  • Accessing an application control without proper interrogation outside of a try-catch block.
  • Using an application control without the validation from a WaitForCreate or IsCreated method.

Resolution of robotic processing issues

Use each tab on the Issues landing page in Robot Manager to investigate any assignment issues. Because each issue type has a different origin, you should use the most appropriate approach when fixing them. Use the following information to help you determine which approach fits each issue.

Automation failures

On the Automation failures tab, you can review each automation to investigate the root cause of the failure or choose to requeue either an individual case or multiple cases at once, as shown in the following figure. If the automation continues to fail, you can further troubleshoot by investigating and possibly refactoring the automation in Pega Robot Studio.

Accessing the Issues landing page in Robot Manager.

Conflicts

You can review each automation that encounters a conflict on the Conflicts tab. Possible fixes for your issue include updating the validation rules or reviewing the format of the values returned by the automation.

Unexpected errors

Review items on the Unexpected errors tab individually. Resolution and further troubleshooting can most likely lead to refactoring in the automation project in Pega Robot Studio. Use the Runtime logs to identify the root cause of the issue.

Time-outs

On the Time-outs tab, you can review each time-out to determine the status of the work completed by the robot, as shown in the following figure. Addition time-out resolutions include:

  • Redesign of the automation for better efficiency.
  • Adjustment to the Max automation run time setting to account for slower than normal automation or application behavior.
Timeouts tab for issues in Robot Manager.

For more information about viewing these issues in Robot Manager, see Viewing assignment issues.

Check your knowledge with the following interaction:


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