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 error occurs on submitting assignment when server quiesced

KCP-151

Summary



When a server is Quiesced, a Lock Lost error occurs and the user is unable to submit assignments. However, on stopping the Quiesce and setting the system status to Running, the user is able to submit the case. 


Error Messages



You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue.


Steps to Reproduce

  1. Work on an assignment. The node enters the Quiesce mode.
  2. Finish the assignment. The lock on the case is lost.


Root Cause



The error occurred because the Locking mode details are stored in the pyCaseUpdateInfo embedded page property in the work page. Since the pyCaseUpdateInfo is a Transient property, the data is no longer present as a result of the Quiesce process.


Resolution



Perform the following local-change to persist the property:
  1. Override the pyCaseUpdateInfo property in the Case class.
  2. Unmark the property as Transient.
Suggest Edit

Published 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