pattern // automationPROJECT
Idempotent Integration Writes
Make retries safe by designing an operation so the same event can be processed more than once without duplicating side effects.
Trust & provenancePROJECT
Evidence tierPROJECTOfficial sources0Other 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.
Problem
Network timeouts and 429/5xx retries can make a caller uncertain whether the previous write actually succeeded.
Approach
Use stable external/event keys, upsert semantics where appropriate, persist processing state and make retry behavior explicit before adding automatic retries.
Requires a stable key or deduplication contract
State management adds implementation work
Not every downstream operation is naturally idempotent