Nintex Workflow Cloud has the following limits to maximize stability and performance. Limit levels are significantly higher than typical usage for most customers. If you anticipate exceeding the limits, reach out to your account manager to discuss alternative solutions or best practices.
User and authentication limits
|Platform||Custom domains in an organization||150||The number includes both verified and pending domains.|
|Platform||Groups in a tenant||200||The maximum number of groups that can be created per tenant.|
|Platform||Groups in a tenant that a user can be a member of||20||The maximum number of groups a user can be a member of in one tenant.|
|Platform||Client Applications per tenant||200||The maximum number of Apps that can be created per tenant.|
|Platform||Personal Access Tokens per tenant||200||The maximum number of Personal access tokens that can be created per tenant.|
Xtensions & Connections limits
|Xtensions||Connections per tenant||1000||The maximum number of connections that can be created for a tenant.|
|Xtensions||Data sources in a tenant||200||The maximum number of data sources that can be created per tenant.|
|Runtime||Total file upload size across all upload controls||250MB||The maximum combined size of all files uploaded to file upload controls in a form.|
|Runtime||Controls in a form||1500||The maximum number of form controls that can be in a form.|
|Engine||Maximum iterations of a loop||1000||The maximum number of iterations in a loop.|
|Engine||Maximum duration of a workflow||1 year||The maximum duration the workflow can be in progress.|
|Engine||Action executions||10,000||The maximum number of action executions in a workflow. This is not the number of actions but the number of action executions. For example, a single loop action with 100 iterations would result in 100 action executions.|
|Engine||Workflow payload size||500MB||The amount of stored data generated by the workflow. For example, a workflow stores generated output data objects — through actions like querying a list — to be used throughout the workflow.|
|Start Workflow Events||SaaS provider with Polling||5 minutes||If webhooks are not supported, the event manager will poll to the SaaS provider at the end of every 5 minutes.|
|Tasks||Maximum duration of a task||1 year||The maximum duration of a task.|
Throttling is common in cloud services and follows the principle that when a resource is requested too many times in a defined period, future requests will be throttled (slowed) or denied (terminated) to ensure other users get fair access to the resource. Following some best practices in your workflow designs can help prevent workflow throttling.
Reduce the number of actions per workflow
If a workflow design has a lot of actions, break the workflow into smaller sub-workflows, and call these sub-workflows using the Start Workflow action.
Most workflows have logical breakpoints within the design where a split can be made. Common breakpoints where a workflow can be broken down include:
Within a Branch by stage or Run parallel paths action: Each branch can function as a sub-workflow.
After conditional checks: Based on the outcome of the condition, the main workflow may start one sub-workflow or another.
Look for opportunities to create component workflows where reusable patterns or processes are repeated within multiple workflows.
Add a pause to long workflow loops
If loop actions are being used within a workflow design, add a Pause for duration action to the workflow after approximately 20 iterations (this number can vary). Add the Pause for duration action inside of a conditional Run if true action within the loop. For example, after every 20 iterations of the loop, the workflow will pause for 1 minute.
Reduce the number of loops and iterations
If loop actions are being used within a workflow design, optimize the workflow by reducing the number of loops and/or iterations within the loops to the absolute minimum.
Reduce Workflow Payload size
If a workflow has a large payload size reduce the payload size by following any of the following best practices:
Reduce the output size for queries and/or Web Service calls. For example, in the Query a List action you can reduce the size of the query or retrieve the minimum number of records and not the full data set/object. Size reduction can also be done by using And conditions to only retrieve the applicable records and querying a fewer number of meta data.
Reduce the number of query and/or Web Service actions that retrieve a high number of records.
Use fewer branches or nested branches, in addition to the two points above. Design a sequential workflow if an available option.
Use loops with fewer actions that retrieve a high number of records (see the first two points).
If multiple unique workflows can be created, break the workflow into separate and unique workflows.