# NetSuite API Retry Backoff Wait Time Calculator > Source: https://netray.co/tools/netsuite-api-retry-backoff-wait-time-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan exponential backoff for NetSuite 429 and concurrency errors: delay per attempt, total wait with and without jitter, and worst case duration. ## Category developer ## Erp NetSuite ## Audience - Integration developer - NetSuite developer ## Tool **Kind:** calculator **Inputs:** #### Initial delay **Key:** base **Type:** number **Default:** 2 **Min:** 0.1 **Step:** 0.5 **Unit:** seconds #### Backoff factor **Key:** factor **Type:** select **Default:** 2 **Options:** ##### 1.5x **Value:** 1.5 ##### 2x (common) **Value:** 2 ##### 3x **Value:** 3 #### Maximum retries **Key:** retries **Type:** slider **Default:** 6 **Min:** 1 **Max:** 10 **Step:** 1 **Unit:** retries #### Maximum single delay **Key:** cap **Type:** number **Default:** 60 **Min:** 1 **Step:** 5 **Unit:** seconds #### Timeout per attempt **Key:** timeout **Type:** number **Default:** 30 **Min:** 1 **Step:** 5 **Unit:** seconds **Outputs:** #### Last delay before cap **Key:** last_raw **Expr:** base * pow(factor, retries - 1) **Format:** decimal **Description:** Seconds. #### Last delay after cap **Key:** last_delay **Expr:** min(cap, last_raw) **Format:** decimal **Description:** Seconds. #### Total wait, uncapped **Key:** total_wait **Expr:** base * (pow(factor, retries) - 1) / (factor - 1) **Format:** decimal **Primary:** true **Description:** Seconds of waiting across all retries. #### Expected wait with full jitter **Key:** jitter_wait **Expr:** total_wait / 2 **Format:** decimal **Description:** Full jitter picks a random delay between zero and the computed value. #### Worst case total time **Key:** worst **Expr:** (total_wait + (retries + 1) * timeout) / 60 **Format:** minutes **Primary:** true **Description:** Waiting plus every attempt hitting its timeout. **Chart:** #### Total wait seconds vs number of retries **Type:** line **X:** retries **From:** 1 **To:** 10 **Steps:** 10 **Series:** - total_wait **Disclaimer:** Uncapped totals ignore the maximum delay, so they overstate the wait once the cap applies. Compare with the capped last delay. Honour any Retry-After header the service returns. ## Content **Intro:** Retrying immediately after a NetSuite concurrency error makes the problem worse. Exponential backoff spaces the retries out, and this calculator shows what that costs in elapsed time so you can choose settings that suit your SLA. **Sections:** #### How to use it **Body:** Set the initial delay, the multiplier applied after each failure and the maximum number of retries. Add a cap so a single wait never grows unreasonably, and enter the timeout of each attempt. The tool reports the final delay, the total wait without a cap, the expected wait when you apply full jitter, and a worst case duration where every attempt runs to its timeout. Use the worst case to decide whether the caller, queue or user can tolerate the delay. #### The formula **Body:** Delay for attempt n equals the initial delay multiplied by the factor to the power n minus one. The sum of a geometric series gives the total: initial delay x (factor^retries - 1) / (factor - 1). With a 2 second start, a factor of 2 and six retries, delays are 2, 4, 8, 16, 32 and 64 seconds, for 126 seconds of waiting. Jitter randomises each delay so many clients do not retry at the same moment, which on average cuts the wait roughly in half for full jitter. **Bullets:** - Delay n = base x factor^(n - 1) - Total = base x (factor^retries - 1) / (factor - 1) - Full jitter: random value between 0 and the delay - Worst case adds timeout for each attempt #### Choosing sensible settings **Body:** For background syncs, six to eight retries with a cap around a minute is common. For user-facing calls, one or two short retries is better, then fail visibly. If many integrations share an account, jitter is essential: without it, a shared outage causes synchronised waves of retries that keep the concurrency limit saturated. Always read any Retry-After header and prefer it over your own schedule. #### Common mistakes **Body:** Retrying on every error type is wrong. Retry concurrency, rate limit and transient network errors, but not validation errors or missing records, which will fail every time. Another mistake is retrying non-idempotent writes without an external ID, which creates duplicates. Finally, forgetting a retry ceiling can leave a job running for hours. **Bullets:** - Retry only transient errors - Use an external ID or idempotency key on creates - Log each attempt with the delay used - Alert when retries are exhausted **Cta:** If your integration loses data on errors, Netray can help design a queue with safe retries and dead letter handling. **Faq:** #### What does NetSuite return when I exceed concurrency? **Answer:** REST calls typically receive an HTTP 429 response, and SOAP calls receive a concurrency related fault. Treat both as retryable with backoff, and check the response for any retry guidance. #### What is full jitter? **Answer:** Instead of waiting exactly the computed delay, you wait a random time between zero and that delay. It spreads retries from many clients over time and reduces repeat collisions. #### How many retries are enough? **Answer:** Enough to cover typical short throttling, usually three to eight, depending on how long the caller can wait. After that, move the message to a dead letter queue for inspection. #### Is it safe to retry a create? **Answer:** Only if the call is idempotent. Use an external ID on the record and upsert, or check for existence before creating, so a repeated request does not make a duplicate. ## Search terms netsuite 429 retry backoff, exponential backoff calculator, netsuite concurrency error retry strategy, retry with jitter netsuite integration, netsuite rest api retry policy, exponential backoff total wait time --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json