Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time

You might be greeted by this error message ‘Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time‘ sometimes when you check the status of a workflow. If there are many workflows trying to run at same time, SharePoint timer service has to push back some of those and queue them for processing later. Timer service does a lot of things behind screen in SharePoint. Timer service instance is installed and will be running on every SharePoint server in the farm. It’s duties include updating components of farm, running services, updating data and configuration and everything else SharePoint does! Running workflows is one of the many things it does. You see the above error if timer service is hit with many workflow instances which it cannot handle all at once.

There are some Farm level settings for workflow management which we can update to improve the overall workflow performance of workflows. But this might have some effect on other thing Timer Service does.

1. Increase Throttle Size: Working throttle size setting controls how many workflows can be processed at any time on entire server farm. Increasing the throttle time, will increase the number of workflows running at any time in the server farm.

2. Increase Batch size: Workflow batch size property controls the number of items waiting in queue to be processed by timer service in every run.By increasing the batch size, more number of workflows can be queue to be processed at a time.

How to Check existing Workflow settings:

workflow settingsThese the default settings for workflow in SharePoint farm.

How to update Workflow Threshold size:workflow thresholdWorkflow Throttle size has been increased to 50.

How to update workflow Batch size:

workflow batch sizeBatch size is increased to 125.

 

 

 

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Disable feedback surveys in Power Platform

If you have worked in Microsoft 365 PowerApps or Power Automate, you might be familiar with feedback survey which pops up quite often. Microsoft wants your feedback on how likely are your to recommend Power Automate to a friend or colleague? Well, I ran into a conversation in twitter about this survey. Apparently I learnt […]

Read More

Error handling in Azure PowerShell Runbooks

Error handling in Azure PowerShell Runbooks should be handled carefully if not the runbook with continue to Completed state even if there is an Error in the script. Unlike exception, Runbook execution will continue after  an Error  by default. Windows PowerShell has multiple streams of output. Runbooks in Azure work differently in each of these […]

Read More

Step by step guide to configure Viva Connections

Update 09/23/2021 – Viva Connections public preview is available now. Steps defined in this article to create an LOB Teams application using PowerShell is not necessary now. Viva Connections app is available in Teams admin center. This new app replaces Step#3 & Step#4 in this article. You still has to go through the home site […]

Read More