When this occurs, filter the ULS logs by using the following condition and check the time of the last entry:

The issue is displayed in the ULS logs before the timer job status becomes 'Pausing.' If no new entries for the 'Timer Job job-workflow' are created In ULS logs, the timer job is stuck. You may also see that the workflow timer job starts on another server if the job can run on that server.Ĭheck the ULS logs every five minutes to see whether the issue was reproduced, and the timer job is stuck. Step 4: Wait until the issue occurs again and collect ULS logsĪfter the configuration cache is cleared, the status of workflow timer job will change from 'Pausing' to 'Paused' and then 'Running.' Wait until the issue occurs-it usually takes ten minutes. Set-SPLogLevel -TraceSeverity VerboseEx -Identity 'Legacy Workflow Infrastructure ' Set-SPLogLevel -TraceSeverity VerboseEx -Identity 'Timer ' Step 3: Clear configuration cacheĬlear the configuration cache on all servers where the workflow timer job is stuck and on the servers where Microsoft SharePoint Foundation Workflow Timer Service is started. In the SharePoint Management shell, run the following command: Step 2: Set ULS logging level to VerboseEx To diagnose the issue quickly, consider stopping the Microsoft SharePoint Foundation Workflow Timer Service on all servers except one. Step 1: Restrict servers that run the workflow timer job (optional but highly recommended) After you verify that, work with the workflow owner to decide whether the workflow can be terminated or deleted. To fix the issue, first determine whether it's caused by a workflow definition that was introduced in the system or by a bad workflow instance. The most likely cause is a bad workflow instance. Workflows don't function over extended periods of time.In SharePoint Central Administration, a workflow timer job shows the status as 'Pausing.' As a result, you experience the following issues: SharePoint workflow timer job is stuck at 'Pausing' Symptoms

Sharepoint 2010 use workflow as timer