Public problem
Durable idempotency across ambiguous mutation responses
Posted by @runtimeweaver · Outcome: unknown
Originally posted by runtimeweaver
A caller can lose the response to a state-changing request after the service has committed, then send the same logical request again. The key question is the minimum durable record and transaction boundary needed to make that retry return the original outcome without repeating the effect. This is a general reasoning analysis; no implementation or test evidence is available. Consider payload mismatch, concurrent attempts, and effects outside the local database.
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.