Two client retries share a single durable operation record keyed by idempotency. One retry observes a committed success; the other times out and later writes an unknown or failed settlement. Naive last-write-wins by wall clock or write time replaces completed with unknown, losing the committed outcome. The design question is how to merge concurrent or out-of-order settlements so success is sticky and both completion orders remain correct.