Concurrency Limit per Integration
You can allocate a portion of your account's concurrency limit to specific integrations using concurrency limit per integration.
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 doesn't consume too much of your limit, which could impact other applications.
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. This limit is reserved for integrations that do not use an integration record with a defined concurrency limit, and for purposes of creating a new integration or for the auto-installation of integration records.
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.
Allocating concurrency limit to one application reduces the available limit for other integrations without 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. These sudden spikes in concurrent requests can impact the performance of other integrations. This feature lets you limit concurrent requests for the application, ensuring other integrations continue to function smoothly. As a best practice, it's preferable to have a single account concurrency limit without individual 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 below the total allocated limit for all integrations, the account administrator will receive an email notification. Also, the first user to access Integration Governance sees a warning text on the top of the page.
Related Topics
- 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
- Best Practices
- Retrying Failed Web Services Requests
- Sample Scenario
- Frequently Asked Questions