Support Article

Submitting assignment throws flow removed error



System throws error "The flow this assignment corresponds to has been removed" on submitting an assignment of a WorkObject (WO). 
Error goes off either by closing the WO and reopening the effected WO or refreshing the browser. 

Error Messages

The flow this assignment corresponds to has been removed. Contact your system administrator to have this assignment deleted.

Steps to Reproduce

1. Create a WorkObject.
2. Try submitting the assignment. 

Root Cause

This is an expected behavior with the below explained root cause. 

Suppose, user "A" opens a tab for worklist "W" which has an assignment “X”.

At that time user “B” has processed the assignment “X”. Now, at this time when user "A" sees the worklist “W”, user will be still able to find the assignment present but with the stale data.

Because the worklist has not been refreshed at User "A's" end. Now when user "A" tries to open the assignment from that worklist, flow removed error comes up.


​Perform the following local-change step: 

Open the assignment from the recent used items or refresh the browser, which gets the data from the database( using Obj-Open-By-Handle).

And hence, it will get the correct data and will be able to see the assignment at the correct flow. 

From the clipboard it is seen that before the work around is applied, the pxLastUpdateBy is "abc" for XXX flow.

But after the work around is applied, pxLastUpdateBy is changed to "xyz".

This clearly states that the assignment is already processed by some other user and hence was the error.

​On performing Obj-Open-By-Handle which gets the correct data from the database, the issue is cleared with no stale data for that Work Object.


Published August 12, 2016 - Updated August 22, 2016

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.