Environment Lock: Timed/Auto Release

[jgregor4]

​It would be beneficial to set a Lock release time on environment locks. As an example, you set 5 minutes, if after that time the lock hasn't been released the system will unlock it.
This would help in instances where the process may freeze while performing actions and the lock then never gets released unless you manually do it in the system settings or the running resource is rebooted.

[robert.nicklin]

Hello @jgregor4,

Thanks for taking the time to raise an idea.

Can you provide a little more information about the scenarios in which you would use a timed/auto release lock? A lot of the time developers want to be explicit about when and how locks are acquired and released as part of a session/general processing task, so I'm wondering how and where you'd prefer more time bound decisions being made.

I'm going to mark this idea as Needs More Info awaiting your response.

Regards,

Rob 

[jgregor4]

Hi @robert.nicklin 

I thought this would be something that could be added to the quite lock action with an input of a set number of seconds. 
if you have an environment lock on a page that you know should take more than a couple of minutes you could put say 240 seconds for an Auto Unlock to occur. 

the reason being, if there is an issue with something on the page or server outage the lock might never get released unless you do it manually in the system settings. 

where there could be pages that have the chance of throwing an exception at various points you do have to be remember to put release locks in multiple places whereas a timed release lock could mitigate forgetting the put these in multiple times.