Request Outcome Lifecycle — Sent, Timed Out, Unknown, Retried, Confirmed Diagram

What a Timeout Actually Means

A timeout is the only signal you get on an asynchronous network: it says nothing arrived in time, not that the request failed
Three different worlds produce the same symptom — the request was lost, the remote node is down, or the reply was lost
The Applied, Unconfirmed state is the dangerous one: the effect is live but the client has no proof

Making Retries Safe

Attach an idempotency key to every mutating request so a repeat collapses into the first effect
With a key, the retry path ends in Deduplicated — one logical effect, however many attempts arrive
Measuring the timeout uses the monotonic clock; a wall clock that jumps backwards breaks the wait loop

How the Bad Ending Happens

Without idempotency, a retry that lands after a silent success produces Duplicate Effect
Duplicates look harmless in testing and corrupt data in production: double charges, double emails, double decrements
Retries must be bounded — an unbounded retry loop turns one slow node into a load storm