> For the complete documentation index, see [llms.txt](https://docs.stacksync.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacksync.com/connectors/netsuite/set-netsuite-concurrency-limits.md).

# Set NetSuite concurrency Limits

* NetSuite caps how many requests run **at once**, account-wide. REST and SOAP share one pool.
* The cap is set by your service tier (+10 per SuiteCloud Plus license):

| Service tier      | Base limit |
| ----------------- | ---------- |
| Shared            | 5          |
| Tier 1            | 15         |
| Tier 2 / Ultimate | 20         |

* **Stacksync never sends more than 3 concurrent requests.** It can only control its own traffic and not other integrations on the account.

By default every integration pulls from the **same pool**. When others get busy, they eat the slots and tip the account over its cap. So errors show up everywhere, including on Stacksync, even though no one is misbehaving.

### Reserve slots per integration

**Setup** > **Integration** > **Manage Integrations** > open the integration > set **Concurrency Limit**.

1. Open the **Stacksync** integration record.
2. Set **Concurrency Limit** to `3`.
3. Do the same for every other integration, sized to its needs.
4. Leave the rest unallocated as a shared buffer.

{% hint style="info" %}
The **MAX Concurrency Limit** field shows how many slots are still free to assign.
{% endhint %}

### Monitor it

**Setup** > **Integration** > **Integration Governance** shows allocated vs. unallocated slots and live usage per integration ([NetSuite docs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/bridgehead_156224824287.html)).

***

Still hitting errors after this? Email <integrations@stacksync.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stacksync.com/connectors/netsuite/set-netsuite-concurrency-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.