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

PR_ASSIGN table is large for case type with stages defined



You notice that the PR_ASSIGN table contains entries for resolved work items with the flow pzinternalstageflow accumulating.

Error Messages

Not Applicable

Steps to Reproduce

Create a case type with multiple stages, work the case to resolved status, then query the PR_ASSIGN table to see if there is a record for the case.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. The logic doesn't currently check if the case is resolved prior to launching


Upgrade to PRPC 7.1.7.

Published April 1, 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