Long NetSuite writes without client timeouts

Problem

A NetSuite RESTlet or SuiteTalk call runs longer than your connector's HTTP client timeout. Holding an open wait through the pool still ties up the client connection for the whole upstream duration.

Fix

  1. Create a Webhook destination your connector can receive.
  2. On the pool Concurrency tab, enable async and attach the webhook.
  3. Send the write with X-Nthpool-Async: 1 (or turn on open wait / queue timeout so slow admits become jobs automatically).
  4. Handle 202 by storing jobId, then process the signed webhook (or poll pollUrl) when the job completes.

The job still uses the pool's concurrency limit, so NetSuite is not over-admitted. Your client no longer needs to stay connected for the full write.

Related