Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Assignments still remain even after transfer or process



Assignments with errors remain on user's worklist after a work object has been transferred or processed.

Error Messages

The flow this assignment corresponds to has been removed

The work object
 references a different assignment than the current one

Steps to Reproduce

Normal case processing.

Root Cause

An issue in the custom application code or rules where explicit commits were made to assignments and work objects during flow processing via the Obj-Save method's "Write Now" option.


Perform the following local-change:

​Remove any explicit commits to the work object or assignment and allow flow processing to handle them, to avoid the potential for assignments and work objects to get out of sync.


Published April 30, 2016 - Updated October 8, 2020

Was this useful?

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us