Issue
Nintex Workflow appears to be 'stuck' in one of the following scenarios:- Workflow contains a State Machine, and appears to have stopped on the 'Change State' action.
- Workflow contains a Pause action and is pausing indefinitely, or for longer than configured.
Resolution
Review the Workflow timer job history
1. Navigate to Central Administration > Monitoring > Review Job Definitions > Job History (upper-left). In the upper-right, apply filters to reflect the following:
View: Job Definition
Job Definition: Workflow
2. Once the Workflow history is populated, ensure that each instance of the Workflow timer job are running in less than the configured interval. For example, if the job is set to run every 5 minutes, a runtime duration of less than 5 minutes is ideal. Otherwise, the interval is violated.
3. Based off of the results of the Workflow History, you might find the following:
- Long-running instances - If you see long runtime durations for instances of the Workflow job, there may be a long-running or infinitely looping workflow executing in the environment. To clarify, the Workflow job is not 'stuck', but is working endlessly to complete some workflow.
- No recent instances - If the most recent 'Completed' date is not recent, navigate to 'Running Jobs' (upper-left) and see if there is a Workflow job running. If so, check when it started to determine how long it has been running for.
- History is empty - The Workflow job may be disabled. To ensure that it is Enabled, click on 'Workflow' (in the Job Title column) and ensure that it is enabled.
If you find that there are long-running instances of the Workflow job, it will be necessary to troubleshoot further with Nintex Support or Microsoft Support to determine what the Workflow job is trying to process.
Additional Information
Continuing a workflow after any Pause or Change State action is the responsibility of the Workflow timer job
