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

Locks held by requestor expire on browser refresh action



Locks held by the current requestor session expire on the browser refresh action. 

Error Messages

Not Applicable

Steps to Reproduce

  1. Acquire lock on a work object or open a work object in perform to acquire lock
  2. Refresh the browser tab
  3. Launch the All Locks landing page to verify the locks 


This behavior is as per the Pega product design. 


The locks are removed by the @baseclass.pyOnbeforeWindowClose activity. Locks expire on unload as per the current functionality. However, Refresh is also an unload event followed by load. If the locks are not cleared, then the work object is stuck to the requestor when the same screen does not load. Hence, all the locks are set to expire on the browser refresh.


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