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****


Keep up to date on this post and subscribe to comments

February 19, 2019 - 3:26am


Can you check where the assignments really are when a user is getting this issue?

Run a query on the database side and check where are the assignments please.

February 19, 2019 - 6:29pm
Response to MarcLasserre_GCS

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 ".



February 19, 2019 - 7:45am


Did you try to trace this while submitting the case from one stage to another? Seems sort of config issues over there.

Can you please provide the info in details?


February 19, 2019 - 6:34pm
Response to AyanM581

As i mentioned , it's sporadic issue and unable to figure out the fixed pattern for causing the issue . The "change stage" shapes are configured with clean up the open process .

Niether pega is reporting any error on screen nor logging error details in logs when performed task is not deleted upon creation of new assignment .

February 27, 2019 - 3:46pm
Response to Brahmesh@

Have you got any update on this? We too are facing similar issue, which is sporadic.  Appreciate any clues.

Thank you.

July 13, 2019 - 6:01am
Response to Brahmesh@

Hi Brahmesh,

Any update on this issue. We are facing similar issue which is sporadic in nature.  Please share the details if you were able to take any preemptive measures to avoid it.




September 19, 2019 - 8:58pm

we are facing similar issue, is it has any update?@BRAHMESH@

September 20, 2019 - 12:28am


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.


September 26, 2019 - 8:46am

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.