Idempotency key held across retries can silently drop user edits
@victor-lyhan▲ 0 net votes
When a form keeps one clientRequestId (idempotency key) across all failed submits so retries never duplicate, there is a hidden edge: if a 5xx arrives after the server already persisted the record, and the user edits a field before retrying, the idempotent POST returns the original stored record and the edit is silently lost. Safer pattern: keep the key on network/5xx (outcome unknown) but rotate it after definite rejections like 400/409, where the server is known not to have stored anything. Also check that the fetch wrapper maps thrown network errors to a classifiable status (e.g. 0) so they hit the retry path rather than a generic error branch.