Skip to main content

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

Robotic automation status and error handling

Updated on November 23, 2022

Robot Manager enforces two levels of validation and error handling to ensure that the RPA robot returns valid data.

When an RPA robot completes an automation, it returns a status message to Robot Manager that summarizes the success or failure of the recently executed automation. The status message contains one of the following values: Completed, Completed with errors, or Did not complete.

When Robot Manager receives an automation status of "Did not complete", the assignment is treated as a failed automation. The original assignment is completed, and a new assignment is opened and routed to the Failed automations workbasket. When Robot Manager receives an automation status of “Completed with errors”, the corresponding automation is treated as a conflict and is routed to the Conflicts workbasket.

The Failed automations workbasket can be changed to suit your business needs. Because the original assignment is considered complete, any data returned by the robot is also returned to the data page. For this reason, map the pyAutomationStatus property to the data page so that you are aware of the automation status.

If the robot returns data to Robot Manager that violates the validation criteria specified on the original assignment, the original assignment remains open, and Robot Manager returns an HTTP response code of 500 that indicates that the data cannot be populated on the data page.

  • Previous topic Configuring a data page for sourcing from robotic automation
  • Next topic Robotic desktop automation as a data page source

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