We have a workflow that was been running without issue for about 9 months that is suddenly failing. It stopped working after the server OS were patched, which happens monthly, usually without issue. The failing workflow is called by a main workflow. The process is as follows:
- Workflow one is started. The workflow controls a data review process and includes users from several departments. The workflow sends a notification to the first user, who has the option to include/exclude certain users, assign a new review completion date, or cancel the review, and then complete the form. Once this form is completed a second form is sent with another task. After the second task is completed, the workflow may start another workflow depending on the response from the first notification (this works). Afterwhich we execute a "Run parallel actions" action. One branch launches the Part 2 workflow and the other branch performs a Pause until the due date.
Part 2 workflow appears to be starting but it never starts. I added a "Log in history list" action as the first step and nothing is logged. The Workflow status has "Note: Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time". After a while this may or may not go away but the workflow never starts.
I increased the workflow-eventdelivery-throttle, workflow-eventdelivery-timeout, batchsize. None of the changes impacted the hung workflow.
I turned on verbose tracing for the Workflow Infrastructure and the last Workflow Infrastructure message that appeared in the log was "Workflow on association 'MDR Routine Data Review Part 2' is about to be compiled". Then nothing else happens.
Does anyone have any ideas as to what may be happening here?
Thanks.