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

Error occurs on creating a child case from a parent case



Error occurs on creating a child case from a parent case and on submitting the first screen or stage in the child case. This occurs despite applying the Locking mechanism in both the parent and child cases.

Error Messages

Parent case is locked by requestor"..."

Steps to Reproduce

  1. Create a parent case and a corresponding child case.
  2. Set the default Locking mechanism.
  3. Select the 'Do not lock parent' checkbox in the Advanced configuration for the child case.
  4. Create a child case. Add the parent case when in another operator.
  5. Submit the first stage or screen of the child case.

Root Cause

This behavior is as per Pega  product design.

Consider two operators,  Operator A and Operator B.

Operator A opened the parent case while Operator B opened the child case in a different browser session. Operator B completed the child case. However, an error occurred in the portal stating that the Cover case was locked.


Here's the explanation for the reported behavior:
  • Default locking – One user at a time can open and work on a case.
  • Optimistic locking – Multiple users can work on a case at the same time.

For more information on Default and Optimistic locking, refer to:

Published November 29, 2019 - 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