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

Lock held error on using Allow multiple users locking strategy

SA-97725

Summary



User creates a case type with the Allow multiple users locking strategy. However, when two users access the same case, the Lock held message displays for one of the users.

Error Messages

Cannot obtain a lock on instance ABC, as Requestor XYZ already has the lock


Steps to Reproduce

  1. Select Allow multiple users for the parent case. The child case inherits it . The child case is instantiated from the browser session.
  2. Open the child case on the mobile application 
  3. Update the child case from the browser session. The error message displays 


Root Cause



An issue in the custom application code or rules. The user explicitly acquired the lock on the case using the Obj-Refresh-And-Lock method in one of the custom activities.

Resolution



Perform the following local-change to release the lock: 
  1. Enable the ReleaseOnCommit option in the Obj-Refresh-And-Lock method
  2. Commit the case in the same custom activity


 
Suggest Edit

Published January 14, 2020 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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