We are facing an issue with periodic workflows which are supposed to run daily. These workflows have their context table set as ‘amWfScheme’. When I check the workflow instance table, there are no 'FINISHED' instances of any of these periodic workflows after 30th July 8 PM.
There were a few 'ACTIVE' instances in the amWfInstance table for these workflows, I removed them and restarted the APM hoping that'd work. It didn't make any difference.
Things that I have checked -
1. The schedule in parameter tab and execution group in APM are exactly the same. It runs daily from 8 AM-9AM.
2. Changed the execution group, logged into APM GUI using service mode and updated the new execution group to mimic the same schedule. This didn't start the workflows either.
3. I've changed the triggering condition and make it a database workflow instead of a Periodic (Log event and Process immediately – bypassing the APM), then modified the field on which Post-update was set to check if the script is getting triggered. It got triggered as usual.
4. I have also re-created one of the workflows from scratch and re-started the APM. Still it's not working.
I am not sure if I am missing a setting somewhere or there is some sort of corruption. We have 7 periodic workflows which have all stopped working after 30th July 8 PM. They were running fine for the past few years.
Please let me know if anything else can be tested, or some ideas to get this working.
Thanks in advance.
Hi Mark & Russell,
It seems to be an issue with the service account we are using. Some compliance requirement on the client side will prohibit supplying service account credentials in a “run as” command on a workstation..
When I logged into the APM GUI using the Admin account, all the workflows were executed as expected with proper entries in the log files.
Thanks a lot for your responses.