This article explains how ExtendInsights interacts with NetSuite concurrency limits and outlines best practices to help you achieve optimal performance when creating, updating, or downloading NetSuite data from Excel.

If you’re primarily interested in optimization tips, you can jump directly to the Best Practices for Maximum Performance section below.

How Does NetSuite Concurrency Affect ExtendInsights?

NetSuite enforces concurrency limits to control how many web services requests an account can process at the same time.

By default:

Integrations using basic credentials (username and password) are limited to one concurrent request
NetSuite also supports Token-Based Authentication (TBA), which allows access to shared account-level concurrency queues

ExtendInsights supports both authentication methods.

ExtendInsights’ Approach

NetSuite enforces strict per account concurrency limits. ExtendInsights is designed to be a good citizen within your NetSuite account.

Current Behavior

ExtendInsights uses one queue at a time, regardless of login method
It does not aggressively consume multiple queues
This minimizes disruption to other real-time or mission-critical integrations running in your account

Example Scenario

If your NetSuite account allows 10 concurrent requests and other integrations are already using all 10:

ExtendInsights requests may be temporarily rejected
The app will enter retry mode (see below)

This approach protects overall account stability.

What Happens When All Queues Are Busy?

Retry Behavior

When ExtendInsights encounters a concurrency rejection:

The request is retried up to 3 times
If all retries fail, the app displays an error
The user must retry the operation manually

This ensures users are notified clearly when concurrency limits are reached.

Future Enhancements

A future version of ExtendInsights will allow admins to define a maximum number of queues that ExtendInsights can use when authenticated via TBA.

This will give customers with higher concurrency limits greater control over performance

How Can I Check My NetSuite Concurrency Limits?

View Account Concurrency

NetSuite Admins can check account limits by navigating to:

Setup → Integration → Web Services Preferences

Look for ACCOUNT CONCURRENCY LIMIT.

This value represents the maximum number of concurrent web services requests allowed.

ℹ️ Follow this cheat sheet from NetSuite to understand your concurrency limits and usage.

Monitor Integration Usage

NetSuite recommends installing the Application Performance Management (APM) SuiteApp to monitor:

Web Services usage
RESTlet usage
Which integrations are consuming concurrency queues

After installation, NetSuite provides a video explaining how to identify and diagnose concurrency issues.

Best Practices for Maximum Performance

Review Scripts and Workflows

NetSuite workflows and scripts can significantly impact upload speed.

Many workflows are intended to run only in the NetSuite UI
If a workflow also runs in SOAP Web Services, it executes once per record during ExtendInsights uploads

💡 Recommendation:
Work with your NetSuite Admin or developer to exclude SOAP Web Services from workflows when possible.

Optimize Upserts (Create & Update Operations)

Follow these best practices when uploading data:

Use internal IDs in [[12345]] format for picklists
Resolve values using Picklist Cell Operations (automatically inserts internal IDs)
Use VLOOKUPs or reference sheets to retrieve internal IDs
Limit columns to only what is required
Avoid including line-level fields unless necessary
Use Background Upload for large datasets

Optimize Downloads

For faster downloads:

Use filters or pre-built Saved Searches to return only required records
Limit columns to what you actually need
Templates without sublists typically download faster

💡 Tip:
If you only need data for reporting (not updates), consider using ExtendInsights Analytics to run and rerun Saved Searches more efficiently.

You can also use Analytics searches to: