Cases getting reassigned to Conflicting robotic automations workbasket
Hi All,
The cases are getting assigned to Conflicting robotic automations work basket after the bot is completing the assignment. In audit it is mentioned as
"Reassigned assignment 'complete task' back to Conflicting robotic automations due to validation failures after automation run."
Please let me know if anyone have solution for this or how to approach this issue.
Accepted Solution
Updated: 28 Oct 2020 2:02 EDT
Pegasystems Inc.
US
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
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
Quest Diagnostics HTAS
IN
Hi Carissa,
We are having the status as did not complete and has invalid data for the cases that are getting assigned to Conflicting robotic automations work basket.
Also can you please let me know on how to trace a work object that a bot is processing. I tried different ways but all attempts were unsuccessful.
Accepted Solution
Updated: 28 Oct 2020 2:02 EDT
Pegasystems Inc.
US
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
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
Quest Diagnostics HTAS
IN
Thanks Rushabh,
After tracing as you mentioned I found that some rules were not deployed to QA environment. So after deploying the missing rules ,now the cases are being marked as resolved properly.
Updated: 19 Nov 2020 7:32 EST
legatohealth
IN
I Am facing the Same issue like , And unable to trace the service mentioned 8.4 and earlier, use the api/v1/assignments/{id} endpoint. If I open the Robotic assignment submit it manually No errors in tracer. Below The audit log we are seeing in PEGA.
Pulled assignment to 'complete task' from work queue RoboWB.
Reassigned assignment 'complete task' back to Conflicting robotic automations due to validation failures after automation run.
ReassignedStart
Unable to find assignee email address to send 'Validation after Robotic Automation failed' to
Infosys Ltd
GB
Hi @SrinivasYalagala, did you got solution, we are facing same issue in our project. Its very random and unable to replicate.