Topic
Workflow start threshold and throttling in Nintex Automation Cloud.
Instructions
Nintex Automation Cloud (NAC) tenants have Workflow Start threshold of 10,000/hour per tenant.
Additional Information
Why does this threshold exist?
- To provide a high-performance environment for all customers, in a fair usage environment.
- Ensure our service operates reliably and predictably for all customers.
- Avoid performance degradation incidents.
- The threshold level is well above the typical usage for most customers. 97% of our Office 365 & NAC customers have workflow starts below 5,000/hour.
What is considered a 'Workflow Start'?
Any request to start a workflow through any of the following channels: Manual start, Form Submission, Start Event (i.e. item added to SharePoint list), Component workflows (i.e. started from NAC API, Start Workflow action, etc.), or a Scheduled start.
How can the threshold be avoided?
- Optimize request operations:
- Add more granular conditions for a request to start workflows
- Fewer requests per hour
- Stagger requests throughout the day
- Reduce the frequency of requests
What happens when the threshold is reached?
- External starts (API calls, component workflows, etc.) - No new workflows start; Returns a 429.
- Start Events - Workflow start is queued and retried in next hour.
- Form submissions - Workflow start is queued and retried in next hour.
- Scheduled workflows - Postponed until the next hour.
Additionally, an in-app banner message in Automate page will be displayed stating the following:
Due to higher volumes within the past hour some workflows have not yet started and are queued to commence shortly. For more information, please visit the manage workflow starts help document.