Hello Rahul,

There are a couple of issues that are resulting in the work item moving to Conflicting robotic automations work queue.

Issue 1: Robot returns Did not complete status

After a robot completes the picked-up work item, at the end and/or part of the automation execution flow there should be a SetCompletionStatus automation block that determines the status it returns to Robot Manager. If this automation block is not part of the execution flow, it sends the case result as Did not complete.

You can find an example here: http://help.openspan.com/191/components/using_the_robotic_case_definition_component.htm?rhsearch=robot%20activity&rhhlterm=robotic%20robot%20robots%20robotics%20activity

If the completed status is Did not complete or CompletedWithErrors. the work item by default will go to the Conflicting robotic automations work queue.

A change in the automation solution is necessary so only in a certain scenario the case status should be returned Did not complete and CompletedWithErrors.

Issue 2: Invalid data Issue

This error generally means that one of the case fields that are updated by the robot doesn’t exist on the pyWorkPage of the work item and/or the data type doesn’t match.

As Carissa said, a tracer should tell us which data is invalid resulting in the error.

For Robot Manager v8.4.2 and earlier, use the api/v1/assignments/{id} endpoint

NOTE: If there is more than one of these endpoints, choose the one that has the higher PegaAPI ruleset version.

For Robot Manager v8.5.1 and later, use the robotics/v2/work/assignments/{id} endpoint

If you are unable to determine the root cause from the tracer, please create a support request and have one of our GCS engineers review the issue with you.

You can open a case from here: https://msp.pega.com/

Thank you