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

The Delete Orphan Assignments gave incorrect response



When using the "Delete Orphan Assignments" button on an item in the Flow Errors screen, accessible from the developer portal with "Designer Studio > Rules and Processes > Processes > Flow Errors", the item doesn't go away.

Error Messages

Not Applicable

Steps to Reproduce

  1. Select an item in the flow-errors screen.
  2. Hit the "Delete Orphan Assignments" button.
  3. Note the error is still there.

Root Cause

This is controlled by the assign-.BulkProcessListView activity, and the item, which is an assignment, is only removed if its associated work object is either missing, or has advanced its flow to no longer be using that assignment.


The selected assignment in the Flow Errors screen will go away when the "Delete Orphan Assignments" button is clicked if the work object flows are no longer using that assignment, or the work object has been deleted. If the assignment isn't removed by the "Delete Orphan Assignments" button, one of the other options on the screen is more appropriate for addressing the problem with the assignment.

Published March 18, 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