A user in a hosted environment noticed that recurring Work Orders suddenly stopped generating. It was found that the Scheduled Action Service, though running, was unable to execute scheduled actions because the user credentials used for the Schedule Action Service were done with a personal account and the account's password had expired.
The user had a generic Network Account created to run the services. the Network Account was then created as a user and employee in APM and the APM Scheduled Action Service in the Windows' Task Scheduler was updated with the Network Account username and password and the service restarted. Once restarted, Work Orders and other Scheduled Actions began running without issue.