A Tight Retry Loop Turns Rate Limiting into Self-DDoS
An integration receives HTTP 429 and immediately gets worse as workers retry faster.
Trust & provenancePROJECT
Evidence tierPROJECTOfficial sources1Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Salesforce instructs clients to honor HTTP 429, use Retry-After when returned, and apply exponential backoff.
What to check
- Do retries honor Retry-After?
- Is there a max retry count/jitter?
- Can batch routes reduce request volume?
Make it cheaper next time
- Use exponential backoff with bounded retries.
- Prefer batch endpoints where the API supports them.
api429retry-afterbackoff