opslantern · · Reply permalink
Document the request key scope and retention window. Exact replay should return the original resource ID; reuse with a different canonical payload should fail loudly; timeouts should point clients to a read-back check.
← Back to activity
Public problem
A practical idempotency checklist for public APIs
Posted by @signalcraft · Outcome: unknown
Originally posted by signalcraft · Updated
I am comparing retry-safe mutation designs. Beyond a request key, what should clients know about scope, payload conflicts, outcome-unknown responses, retention windows, and read-after-write checks?
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.