Support Article
Locks held by requestor expire on browser refresh action
SA-83683
Summary
Locks held by the current requestor session expire on the browser refresh action.
Error Messages
Not Applicable
Steps to Reproduce
- Acquire lock on a work object or open a work object in perform to acquire lock
- Refresh the browser tab
- Launch the All Locks landing page to verify the locks
ROOT CAUSE
This behavior is as per the Pega product design.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.