Govern concurrency of NetSuite connections

Requests to NetSuite APIs are governed by the following factors:

• Concurrency limits placed on combined web services and RESTlet requests, per account
• Limits placed on each integration

If the number of concurrent requests exceeds these limits, then subsequent requests may be rejected. integrator.io provides you with the means to control the concurrency for a connection to NetSuite.

NetSuite account-level limits

This limit applies to the combined total of SOAP Web Services and RESTlet requests across your NetSuite account. This maximum request count is calculated by your NetSuite service tier, the number of SuiteCloud Plus (SC+) licenses, and account type. You may contact NetSuite to purchase additional concurrent requests if you need more throughput.

NetSuite integration limits

In addition to account-level limits, NetSuite allows you to set the concurrency on each NetSuite integration. By changing the concurrency limit per integration, you can ensure that a specific integration has the required bandwidth and does not use too much of your limit, blocking other applications from working smoothly.

View and change your concurrency limits in NetSuite

To see and manage your available concurrency limit, go to Setup > Integration > Integration Management > Integration Governance (Administrator).

Note: As the Rejected Requests Ratio increases, the total concurrent load being placed on NetSuite by your client apps, including integrator.io, is exceeding the concurrency limit for your account. In this case, consider adjusting the distribution of concurrent calls across the other applications.

To see and manage your available concurrency limit:

1. Go to Setup > Integration > Manage Integrations (Administrator), and choose from the list of integrations.
2. Select an integration to change its concurrency limit.
3. Enter your changes in the Concurrency Limit field and click Save.

View your web services usage

1. Click the Setup menu.
2. Select Integration > Web Services Usage Log from the list.

For more details on concurrency governance, visit the Oracle NetSuite Concurrency governance topic.

Set concurrency limits in your connections

Each connection has its own concurrency setting, which controls the maximum number of concurrent requests the connection can make. The concurrency level should match that in your NetSuite account. Keep in mind that you must re-authorize each connection when you save edits. 

Tip: If you need, for example, more throughput than 25 concurrent requests for a single connection resource, consider creating a second connection resource and partitioning your flows across different connections.

Considerations

If your NetSuite integration is running slowly, you can consider adjusting the concurrency level to allow multiple transactions to happen in parallel. However, since each connection to NetSuite has its own concurrency setting, it is important to assess the maximum number of concurrent requests your integrations may make and compare that with your NetSuite limits. Exceeding the concurrency limit can result in disruption of your flows.

There may be additional platform applications that access your NetSuite account.  Assign each the appropriate number of calls so that the total concurrency limit is not exceeded. 

Identify the performance bottleneck

• Is it NetSuite, the other endpoint, or both?
• On the dashboard, view the timestamps for each flow step.
• Identify which step is consuming the most time. 

Verify existing configuration

• If the concurrency level is set to a lower value than supported, increase it.
• Check if Export type is set correctly (All vs. Delta, and so forth).
• Monitor the performance for a day or two to refine the configurations. 

See also

• Error: SSS_REQUEST_LIMIT_EXCEEDED
• Handle NetSuite point limits (troubleshoot error code: ss_out_of_points)