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

Commit does not release lock for parent case post upgrade



The parent case lock is acquired when resolving the child case post upgrading to Pega 8.2.2.

In Pega 7.2.2, the final commit releases the lock for both the cases. However, in Pega 8.2.2, the commit does not release the lock for the parent case.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a parent and child case hierarchy with default locking
  2. Select the Do not lock the parent case checkbox
  3. Submit the child case. Final assignment results in the parent case lock being held

Root Cause

A defect in Pegasystems’ code or rules.

In the Work-.Resolve, the openIfStale engine API is invoked with eight parameters (important parameters among the eight are: aUnlockOnCommit – true and maintainLockingStrategy – true). This is where the lock is acquired; and post commit, the lock is released.
For this type of locking configuration, the combination of the parameters (mentioned above), behaves differently. Hence, the lock on the parent case is not released. This method from the engine has modifications since Pega 7.4 with various checks based on the parameters.


This issue was reported as a bug to be remediated in Pega 8.2.4 , Pega 8.3.1 and Pega 8.4 patch releases.


Published 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