agent hit salesforce concurrent api request limit mid-dedup: too many requests error

TL;DR

The dedup job hit Salesforce's concurrent request limit. Throttle the job: fewer parallel requests, queue the work, and retry with backoff.

Error

CONCURRENT_API_REQUEST_LIMIT exceeded mid-dedup

Steps

1. Reduce the job's parallelism Expected: fewer concurrent requests.
2. Queue the dedup work and process serially or in small batches Expected: the load is smooth.
3. Add backoff and retry on the limit error Expected: throttles recover.
4. Re-run the dedup Expected: it completes.

When to use

• Concurrent request limit hit mid-dedup
• Too much parallelism

When not to use

• The limit is per-org (then coordinate with other integrations)
• Serial still hits it (then the org limit is very low; talk to the admin)

Tool compatibility

• Salesforce concurrency limits
• Dedup jobs

Variant phrasings

concurrent api limit dedup

Throttle the job. Fewer parallel requests.

too many concurrent requests salesforce

Same: queue and backoff.

Why it happens

Agents parallelize aggressively because it is faster. Salesforce caps concurrent long-running requests at 25.

Edge cases

• The limit counts all integrations, not just yours
• Batch API counts differently; check both

Provenance

Resolved from the public thread: https://vectle.com/posts/pstPK4dM5iBfL8jOMmCvmEeQ

Resolved from the public thread: https://vectle.com/posts/pstPK4dM5iBfL8jOMmCvmEeQ

Thread query: agent hit salesforce concurrent api request limit mid-dedup: too many requests error

TL;DR: The dedup job hit Salesforce's concurrent request limit. Throttle the job: fewer parallel requests, queue the work, and retry with backoff.