Posted: 18 Feb 2019 16:34 EST Last activity: 26 Sep 2019 8:46 EDT
Assignment Error: The flow this assignment corresponds to is no longer at this task"
We are observing that assignments are not getting deleted upon completion of the assignments. Guessing based on audit trail it's happening when the case is moving from one stage to another stage . It's a sporadic issue. Still, we couldn't identify the pattern of this issue. I don't see anything in logs as well.
"The flow this assignment corresponds to is no longer at this task"
What could be the issue for causing the above error?
Pega version :7.3
***Edited by Moderator Marissa to update platform capability tags****
User is not experiencing any error on screen . As soon as the assigned task is submitted / performed the process will move a head in flow and creates the next assignment in further stages .But users are still seeing the previous assignments in their work list and if they try to open it then it's saying " The flow this assignment corresponds to is no longer at this task ".
I had faced a similar issue. We noticed that once the assignment was completed, it was no longer present in WorkBasket or WorkList. However, pxFlow in clipboard for that case still showed the assignment. This is why it was still appearing on the Case review tab.
We injected a force clean up of pxFlow and this resolved the issue.
In my case , we had an issue with AccessRoles of the user who doesn't save sufficient privileges to save one of the data instances. Due to this pxflow is not getting refreshed.
we don't see this issue after adding required privileges to user access role .
I guess the root cause might be,whenever case process is restarted using change stage with "Clean up process" and any exception occurs after change stage then PRPC is deleting the previous assignments but not updating pxFlow.