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

pyStatusWork is overridden to Resolved-Unspecified



All the statuses (For example: Active, Retired, Resolved) are overriden to Resolved-Unspecified post upgrading to Pega 8.1. Initially, the status is changed to Resolved and later it is overridden to Resolved-Unspecified.

If the user does not provide status values, the current case is set to Resolved-Completed and open child cases are set to Resolved-Unspecified. This is mentioned in the Case Resolution of the help document. However, the current case is not a child case.

Error Messages

Not Applicable

Steps to Reproduce

  1. Upgrade Pega 7.4 to Pega 8.1.2
  2. Set the work status to Resolved in the end shape of the previous process
  3. Run the case. The status is set to Resolved initially and later it is overridden to Resolved-Unspecified

Root Cause

A defect in Pegasystems’ code or rules. The  Workstatus configuration is different on Pega 8.1. If a stage is marked as resolution and the status is not provided, it is marked as Resolved-Unspecified in the resolution.


Here’s the explanation for the reported behavior:
Design time validation is already present indicating that a status other than Resolved- cannot be provided. The changes are added to Sync at runtime and design time behavior on Pega 8.1.


Published August 19, 2019 - Updated December 2, 2021

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