Salesforce
Designing Idempotent Integrations
The retry is not an edge case. It is the normal case. Designing as though it were is the difference between calm systems and pager fatigue.
COVER IMAGE — 16:9
Every integration fails. The only question is whether your system treats the second delivery of the same message as a duplicate or as a disaster.
Make the second call boring
An idempotent endpoint can receive the same event twice and produce the same result once. You get there with stable keys, dedup at the boundary, and operations that describe a desired state rather than an increment. Do that, and retries stop being something you fear.