Why is my state machine taking so long?

Hi Nina,

if you are using the state machine, the tranisition between the stages is realized by the workflow timer job. The workflow timer job is (by default) scheduled to run every 5 minutes. That means, when your workflow is reaching the "Change state" action, the state does not change immediately but has to wait for the timer job to get the work done. Imagine the timer job like a bus that is driving every 5 minutes and your workflow is waiting at the bus stop. If you are lucky, the workflow will be ready and the bus (timerjob) is just about to come in some seconds. But in the worst case you have to wait 5 minutes + additional time the timer job needs in case of heavy load on the system (a lot of traffic because holiday time is about to end).

It does not necessarily has to be something wrong in your system, this can be normal behaviour.

However, you can either reschedule the job to run every minute (this is the minimum) or you can start it manually ("run now" option). Both can be checked/updated in the central administration of sharepoint by navigating to Central Administration Site -> "Monitoring " -> "Review Job Definitions" -> Click on Job Definition with Title "Workflow":

Here you can lower the time between job executions or start it manually (by clicking "Run Now").

Safe looping could be the reason only if you have extensive looping logic inside of your workflow, which I don't see any indication for yet but we would need to see your workflow to be sure.

For restarting the timer service you have multiple options.

1. You can do this via Windows Server OS (Start Menu -> type "Services" -> find and restart "SharePoint Timer Service"):

2. You can do it via PowerShell:

restart-service sptimerv4

3. You can do it via Command-Line:

net stop SPTimerV4

net start SPTimerV4

I have never experienced any problems when restarting the timer service. But if you want to be on the safe side, don't do it in your main business hours

Cheers

Philipp