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

An error message is displayed when the case remains idle



The default case time out is set to 30 mins. So if at the 29th min the user fills in a request form. At the 30th min the lock becomes a soft lock. At this point an Service level rule runs to take over 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. Create a case
  2. Open the case in perform mode and do not action on the same
  3. After few minutes, user sees the error message on the screen.

Root Cause

With Pega 7 the Lock caching is enabled for better performance and invoking LockManager.Lock() has no effect. Increasing timeout at 29th min is custom requirement which is needs to be addressed as an enhancement request.


If users are making changes at 29th min which reports the error message, try to increase the locking time(from default time of 30min) as per the business requirement.

For the custom business requirement, you can always use Obj-Refresh-And-Lock method to reacquire a lost lock given that it has not already been locked by a different requestor.

Published March 12, 2017 - 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