Certain robot machines have a consistent issue with sending case results. A log excerpt is below, with identifying characteristics masked. The log excerpt is from a Completed with Errors result, but we see exactly the same error on a Completed result.

When the same robot automation is activated on a different robot VM, these errors do not occur. But we have several VMs on which these errors are consistently occurring.

Is this an issue with the Operator in Pega or the VM itself? Is something corrupted in the Robot Runtime? Corrupted on the VM? The errors do not show up in Pega itself, only on the robot VM.

Case result not sent log:

ERROR | 2020-12-08 11:40:14,224 | PA Work | 24  | 83740 | MTA   | Robotics                  |                                |                                | RoboticsApiHelper.SendCaseResult - Error POST case result. Case completion status: 'Completed with errors'. Error: 'One or more errors occurred.'. ERROR | 2020-12-08 11:45:14,668 | PA Work | 24  | 83740 | MTA   | Robotics                  |                                |                                | RoboticsApiHelper.SendCaseResult - Send case result failed. Case completion status: 'Completed with errors'. ERROR | 2020-12-08 11:45:14,668 | PA Work | 24  | 83740 | MTA   | Robotics                  |                                |                                | Error requesting data from Pega. MASKED_URL/prweb/api/v1/assignments/ASSIGN-WORKLIST%20MASKED%20A-1155937!PZCREATEROBOTICASSIGNMENT?actionID=pyCompleteAutomation ERROR | 2020-12-08 11:45:14,668 | PA Work | 24  | 83740 | MTA   | Robotics                  |                                |                                | Code: NotFound(404), Content: { "pxObjClass":"Pega-API-CaseManagement-Assignment" ,"errors":[  { "ID":"Pega_API_006" ,"message":"Assignment not found for the given parameter ID" ,"pxObjClass":"Pega-API-Error" } ,{ "ID":"Pega_API_006" ,"message":"Assignment not found for the given parameter ID" ,"pxObjClass":"Pega-API-Error" } ]  }