If you’ve been receiving the following error message when kicking off a workflow:
“Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time” is coming sometimes”
… well, you’re not the only one. The above issues do not necessarily mean you have to throw more hardware at the server. Especially is some other symptoms include: workflow initiation taking a long time, workflow emails taking longer to be sent. There are few configurations you can implement, such as:
-Increase Throttle Size
-Increase Batch Size
Throttle size for example is a farm setting which is a max number of concurrently running workflows on the farm; default is 15, but often that’s not enough. To check the throttle size on your server run the following PowerShell command:
Get-SPFarmConfig | Select WorkflowPostponeThreshold
Or set it to a new number using this command:
Set-SPFarmConfig -WorkflowPostponeThreshold 50
Batch size is a number of items that are allowed in the queue of the Timer Service. Since Timer Service handles lots of other services, workflow is not necessarily its main priority. To check what’s your batch size run the following PowerShell command:
Get-SPFarmConfig | Select WorkflowBatchSize
Or set it to a new number using this command:
Set-SPFarmConfig -WorkflowBatchSize 150
Enjoy!
This article was originally posted here.
Is there a way to see how many items are in the throttle or batch? Rather than just changing the values blindly, I would like to see how many of each I have first.