Users may occasionally receive warnings such as:

"SuiteTalk concurrent request limit exceeded. Request blocked."

This article explains why this happens, how CloudExtend manages concurrency, and what you can do to improve performance.

Applies to the following products:

ExtendInsights for Excel NetSuite
ExtendSync for Outlook NetSuite

Understanding NetSuite Concurrency

NetSuite restricts the number of simultaneous web services requests your account can process.
These limits vary by account type and licensing.

Defaults & Limitations

Integrations using basic credentials (username + password) are limited to one web services call at a time.
Integrations using Token-Based Authentication (TBA) can use multiple queues, but are still subject to the overall account concurrency limit.

CloudExtend supports both authentication modes.

CloudExtend’s Current Approach

e want to be a team player with all of your other apps and not be overly aggressive in taking over queues.

✔ CloudExtend only one web services queue by default

Presently, CloudExtend apps are deisgned to use only one queue. Regardless of authentication method (basic credential or TBA), CloudExtend will intentionally limit itself to a single queue.

Why?

Prevents CloudExtend from dominating your concurrency resources
Minimizes impact on other integrations (SuiteTalk, RESTlets, EDI, custom integrations, etc.)
Ensures stability across all systems using NetSuite in real time

What this means in practice

If your NetSuite account allows 10 concurrent requests and other integrations are using all 10, CloudExtend will:

Detect that no queue is available
Retry automatically (details below)
Notify the user if retries fail

A future build of CloudExtend may allow admins to specify a maximum number of queues for CloudExtend when using TBA. Customers with sufficient NetSuite queues will have full control over CloudExtend performance.

CloudExtend’s Retry Logic

In the event all of your NetSuite queues are occupied CloudExtend Apps have a built in retry mechanism. Whenever the app notices that one of it’s requests are rejected due to concurrency restrictions, it will do the following:

Waiting period:
- The app waits 5 seconds
User notification:
- A message appears:
  “No NetSuite queues available.”
Retries:
- The app retries every 5 seconds, up to 4 additional attempts (5 total tries)
If still unsuccessful:
- CloudExtend surfaces an informative error
- The user must retry the operation manually

In the event a queue does not become available after the 5th try users will see an appropriate failure notification in the app and they will be required to retry the operation they were performing before.