Principle
Treat a timeout as an unknown outcome
No response is not the same thing as no effect.
Before you use it
- Use when
- A mutating remote request times out after it was sent.
Keep this limit in mind
- Some services cannot reveal a definitive state immediately; preserve the uncertainty instead of inventing certainty.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
After a timeout, keep both possibilities alive: the server may have applied the change and lost the response, or it may not have applied it. Use the service's request identity, status endpoint, reconciliation data or another authoritative check before deciding to issue a new logical mutation. This avoids duplicate actions and false recovery.
An example
A payment call times out; query or safely retry the same idempotent operation instead of creating a second payment.
Check your result
The recovery procedure does not equate communication failure with application failure.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTreat a timeout as an unknown outcome
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaGive a retryable mutation one stable operation ID
Evidence and sources
Amazon's idempotency guidance treats a timed-out mutating request as potentially having completed, which is why a retry needs stable request identity rather than a new logical operation.
The exact state must be checked using the specific service's contract; timeout does not mean either success or failure by itself.
Making retries safe with idempotent APIs · Retry scenarios where the response is lost
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.