If an assignment is not successfully processed (an automation failed for that assignment), you can re-queue it so that it can be processed again, or you can skip the processing of the automation by manually continuing the flow in a case type. You can also re-queue multiple failed assignments at one time.
Because Pega Robot Manager cannot determine which parts of an automation were completed before any errors occurred, it is best practice to investigate any failed assignments before re-queuing.
If an assignment did not complete successfully, one of the following status notifications is returned to Pega Robot Manager:
- Completed with errors – the robot attempted to complete the assigned work, but the automation detected a problem when attempting to run. For example, the required application was not available at the time, or the automation was not able to execute because some input values were incorrect. After resolving any issues, you can re-queue such assignments. If the automation continues to fail, this may require further troubleshooting and refactoring in Pega Robot Studio.
- Did not complete – the automation encountered an unexpected error, and did not complete the assignment for an unknown reason. Manual intervention is needed for each such failed assignment. The failing automation might require further troubleshooting and refactoring in Pega Robot Studio.
- Processing a failed assignment
You can re-queue a single assignment so that it can be processed again, or you can manually continue a flow in a case type to skip the processing of an automation.
- Processing multiple failed assignments
You can re-queue multiple failed assignments so that they can be processed again.
- Downloading robot activity logs
Identify the causes of automation failures by reviewing robot activity logs. At the time of a failure, Pega Robot Runtime creates a robot activity log that you can download from Pega Robot Manager in a ZIP file.