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

Many inconsistent Work Objects (assignment error)



During the execution of an activity which writes XML files, a hard drive of an external system runs out of space.

The activity normally catches the exception and sets the status to "Fail". But in this case the status was not set and hence, the work objects still hang in this utility shape as last step and do not have any assignment left.

Error Messages

Not Applicable

Steps to Reproduce

There is no specific use case to reproduce this issue.

Root Cause

This is an environmental problem. The normal behavior of the WorkObject has been broken and a custom repair is needed.


Implement the below local-change to resolve this issue.

1. Create a custom activity to open the WorkObjects with “Obj-Open-By-Handle” method.
2. Delete the broken assignment by removing the corresponding “pxFlow()” page.
3. Call Out-Of-The-Box Work-.StartNewFlow to restart the process.

4. It is also necessary on the new pxFlow() page generated to add the following properties, for the parent flow to be recognized:


Published August 10, 2015 - 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