User noticed that several work orders slated to be automatically closed were still open. When the user tried closing the work orders manually, APM would launch a dialogue indicating that the work order were still being edited by an automated service user.
There are many different times of scheduled actions: some focus on closing work orders, some focus on generating new PMs, etc. Any one of these actions may hang for various reasons and when they hang the transaction in process may continue to keep locks on the objects being worked on and will hang indefinitely if there is no timeout set on the scheduled action. The section of the help file that shows where to set the timeout, the "Stop running after" attribute is:
https://help-apm.bentley.com/7/en/eam/wwhelp/wwhimpl/js/html/wwhelp.htm#href=Creating_Scheduled_Actions.html<https://urldefense.com/v3/__https:/help-apm.bentley.com/7/en/eam/wwhelp/wwhimpl/js/html/wwhelp.htm*href=Creating_Scheduled_Actions.html__;Iw!!AwIW5cuGsw!dGFoCH2f54lTZvGUf0qCvNOu1eS5l_zOfkxs9TFcLNv9DoUp_3jlTVF88g2Agq8X8Asqkv-IIZfHUov-Y9aI$>
You can find this on the enterprise level.
The "Stop running after" property should be set this for all scheduled actions, keeping in mind to lengthen and shorten the period for each based on previous history for that particular scheduled action. Most scheduled actions should be set to 1 hour and no scheduled action should need to be set to more than 8 hours.
Note - We setting this, also consider the time that the scheduled action is set to run at and set the Stop running after time that will avoid the scheduled action running during a database back-up time as this can result in conflicts with scheduled services creating new objects at the same time a back-up is being taken.