Topic

 
Nintex Workflow Cloud (NWC) 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 O365 & NWC 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 NWC 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.
 

Configure your Nintex Gateway .NET Core and .NET Framework proxies.

Topic

Frequently asked questions about Data Source Variables in Nintex Workflow Cloud Forms.
 

What are Data Source Variables?

Data Source Variables are a new capability that is available within Nintex Workflow Cloud Forms that enables designers to source data from external systems into their forms design and use that data across various different controls and rules. Like the Data Lookup control, Data Source Variables leverage existing data sources within Nintex Workflow Cloud to connect to external systems but aim to provide more flexibility with the data than the drop-down styling of the Data Lookup control.

Can anyone create a Data Source Variable?

Designers that have been given permissions to a data source within Nintex Workflow Cloud can create new Data Source Variables.

Can Data Source Variables be used with any control type in Nintex Workflow Cloud?

Currently Data Source Variable values can be used with Label controls and can be set as the value of Text – Short, Text – Long, Email, Currency, Number, or Geolocation control via rules. Support for additional controls such as Choice – Single and Choice – Multiple will be available in the future.

Can any data source be used to create a Data Source Variable?

Currently Data Source Variables only support SharePoint Online and Azure Active Directory data sources, however additional data sources will be made available in subsequent releases.

Can a custom Xtensions based data source with Data Source Variables?

Not yet, but this functionality should be available soon.

Can I use my Data Source Variables within my workflow?

While any values that are used in a control will be passed to the workflow as a start event variable, the Data Source Variable itself is only available within Forms at this time. If a workflow designer would like to access the same information, they can use a ‘Query’ action as this will return the same object/data as the Data Source Variable.

Additional Information

Related Links