How can the end user limit AppLink’s NetSuite concurrency usage?

If you are concerned that AppLink could use too much of your NetSuite account’s API concurrency, you can set an integration-specific Concurrency Limit directly in NetSuite.

Concurrency means requests running at the same time, not a daily or per-minute request allowance.

This is both a cap and an allocation. NetSuite limits AppLink to its assigned concurrency, but also sets that capacity aside from the account’s shared, unallocated pool. It does not add capacity or mean the integration has no impact on the account’s total budget. Oracle: Concurrency Limit per Integration

Before you start

Sign in to the correct NetSuite account as an Administrator. Choose a limit with your NetSuite administrator that leaves enough capacity for your other integrations.

These steps apply to requests using the AppLink integration record. If your connection uses a differently named integration, or you see several similar records, confirm the correct record with Rutter before changing it.

Set the limit

1. Open the NetSuite Integrations list. NetSuite may redirect this link to your account-specific domain. You can also navigate to Setup → Integration → Integration Management → Manage Integrations.

2. Click AppLink, then click Edit.

3. Find Concurrency Limit near the top of the record. Note its current value so you can restore it if needed.

4. Enter the number of simultaneous requests you are comfortable allocating to this integration—for example, 2, if appropriate for your account. Do not exceed the displayed MAX Concurrency Limit. Leave authentication settings and the integration’s Enabled state unchanged.

5. Click Save. Confirm the success message and that the record shows the value you entered.

What to expect

NetSuite rejects requests that exceed the applicable concurrency limit; the integration needs to handle these errors and retry. A lower limit can therefore increase throttling and slow synchronization. This setting is not a guarantee of unchanged sync speed or of zero concurrency errors. Oracle: Errors Related to Concurrency Violations · Oracle: Concurrency FAQ

For example, in our sandbox test:

Other integrations without a dedicated limit share the remaining unallocated pool. NetSuite requires at least 1 slot to remain unallocated. Oracle recommends using per-integration limits when there is a specific need, such as controlling an integration’s concurrency spikes. Oracle: Concurrency Limit per Integration

Verify and monitor

Go to Setup → Integration → Integration Management → Integration Governance. Check the account limit, unallocated limit, and AppLink’s assigned limit.

If your account has the APM SuiteApp and the required access, use Customization → Performance → Concurrency Monitor to review allocated and unallocated usage. Oracle: Concurrency Monitor Overview

If sync performance becomes unacceptable, review the allocation with your administrator and Rutter. To undo your change, return to AppLink → Edit, restore the previous value, and Save. If it was originally blank, clear the field to return the integration to the unallocated pool.