Concurrency limit per integration allows you to allocate part of your account's concurrent requests limit to specific integrations.
You can use concurrency limit per integration to ensure that:
The specific integration to which this limit is allocated has the required bandwidth to function.
The specific integration to which this limit is allocated does not use a too big part of your limit, blocking your other applications from working fluently.
To see and manage your available concurrency limit, go to Setup > Integration > Integration Management > Integration Governance.
Under Concurrency Usage you can view the account concurrency limit and the unallocated concurrency limit
The minimum unallocated concurrency limit value is one.
Under Concurrency Limits per Integration, you can see a list with all integration records, their state and the concurrency limit that has been allocated to them. If you are the owner of the integration, you can also see the Application ID.
When allocating part of your account's concurrency limit to one application, you reduce the available concurrency limit for other integrations, which do not have a specific limit.
You should only use this feature if you have a good reason to do so. For example, you may have an external application that you do not fully control, and which occasionally sends a high number of concurrent requests. This sudden increase in concurrent requests can cause issues to other integrations. With this feature, you can now limit the number of concurrent requests allowed for this application to protect the functionality of the other integrations. It is a best practice to have one account concurrency limit, without limits for each integration.
To manage the concurrency limit per integration, click the name of the integration to open the integration record.
Here you can enter the value for the concurrency limit you want to allocate in the Concurrency Limit field. In the MAX Concurrency Limit field, you can see the unallocated concurrency limit that is available to allocate.
The value of the MAX Concurrency Limit field is always one less than the total unallocated concurrency limit of the account.
If your subscription for company Service Tier or the number of SuiteCloud Plus licenses expires, your account concurrency limit will reset to the default value. If the account concurrency limit decreases by that to a value lower than the sum of the allocated concurrency limit per integration, the administrator of the account receives a notification per email. Also, the first user to access Integration Governance sees a warning text on the top of the page.
- Web Services and RESTlet Concurrency Governance
- Concurrency Governance Limits Based on Service Tiers and SuiteCloud Plus Licenses
- Concurrency Governance for Internal Applications
- Effects of Authentication Method on Concurrency Governance
- Account Concurrency Monitoring Resources
- Errors Related to Concurrency Violations
- Recommended Actions
- Retrying Failed Web Services Requests
- Sample Scenario
- Frequently Asked Questions