Netsuite has concurrent request limits that have effected several of our Netsuite and HubSpot integrations, causing some consternation and confusion for our clients.  If multiple integrations or external applications are running and making API calls, concurrency errors (and thus failed record syncs) can be common.

The number of concurrent requests available to a client is derived from their service tier, Suite Cloud + Licenses, and their account type.  TBA (Token Based Authentication) provides unlimited calls per user, but overall Account limits still apply. These limits apply across SOAP, REST Web Services, and RESTlets.  

Clients can typically see their Account Concurrency Limit by navigating to Setup>Integration Governance.

With the release of Netsuite 2019.2 in October, clients will be able to "prioritize" certain integrations over others by defining the number of concurrent requests available for that integration that will NOT be rejected, even if other integrations or applications are performing concurrent API requests. 

Clients will have access to the above menu (again, in Setup>Integration Governance) and will have the option of selecting a concurrency limit for a specific integration.  In the above screenshot, the max concurrency limit is "15, and so if "15" was entered as the concurrency limit for this specific integration, Netsuite will allow the maximum number of concurrent requests for that integration and potentially disallow requests from other integrations or applications.  This obviously has ramifications and should be carefully considered by the client prior to enabling.

As an example of the above, if our LyntonWeb Integration was set to "15" below (and assuming, again, that 15 is the account concurrency limit), it would be prioritized by Netsuite and possibly disallow API requests from the other applications in this organization, such as the TPS integration in this case:

Clients can also monitor concurrency via Netsuite Concurrency Monitor dashboards. These will detail daily and hourly concurrent requests and provide information as to rejected calls as well.  Navigation is Customization>Performance>Concurrency Monitor as shown here:

It is important to note, however, that the above does not address the Account level Concurrency limit.  At this time the only way to increase this limit is to:

  1. Service tier upgrade:  This provides five (5) additional requests per level.  There are 3 service levels.
  2. Additional Suite Cloud + licenses.  Each license provides ten (10) requests.  Client's can use the above Concurrency Monitor Dashboards to calculate how many licenses they require to avoid concurrency limits.  Purchasing additional licenses appears to be the optimal way to increase Account level concurrency limits.
  3. Change/upgrade Account type.  Additional concurrent requests can be customized.

With Netsuite 2019.2, Clients have tools to manage concurrency issues and visibility into the number Account level limits and various requests.   Clients will need to contact their Netsuite representative should they experience more concurrency errors than is acceptable to them and purchase additional Suite Cloud licenses.