Why is my workflow timer job stuck on another server?
You may also see that the workflow timer job starts on another server if the job can run on that server. Check the ULS logs every five minutes to see whether the issue was reproduced, and the timer job is stuck. The issue is displayed in the ULS logs before the timer job status becomes “Pausing.”
Where do I find the timer job in SharePoint?
Go to Start -> Administrative Tools -> Services -> Find the SharePoint Timer Job -> Right Click -> Start Note: The file system cache is re-created after you perform the previous steps. Make sure that you perform these steps on all servers in the farm that are running your timer job
Why is my SharePoint timer stuck at 0%?
Ran into a problem recently where the Workflow Timer Job on our SharePoint 2010 box was stuck at 0% and Paused. Restarting the Timer Job and trying to kick off again did not provide the fix I was hoping.
What happens when I clear the configuration cache?
Clear 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. After the configuration cache is cleared, the status of workflow timer job will change from “Pausing” to “Paused” and then “Running.”
How long does it take for workflow timer to run?
After 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. You may also see that the workflow timer job starts on another server if the job can run on that server.
What happens to workflow timers in SharePoint central administration?
In SharePoint Central Administration, a workflow timer job shows the status as “Pausing.” As a result, you experience the following issues: Approvals of tasks don’t complete. Workflows can’t run after a pause. Random processing of workflows occurs. Workflows don’t function over extended periods of time.
What happens when timer job is stuck in ULS?
If no new entries for the “Timer Job job-workflow” are created In ULS logs, the timer job is stuck. When this occurs, filter the ULS logs by using the following condition and check the time of the last entry: Find the last workflow that was being processed.