# Treat a timeout as an unknown outcome

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Treat a timeout as an unknown outcome

ID: MHC-D-RESEARCH-0349 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/treat-a-timeout-as-an-unknown-outcome

No response is not the same thing as no effect.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A mutating remote request times out after it was sent.

### Avoid when

- Some services cannot reveal a definitive state immediately; preserve the uncertainty instead of inventing certainty.

### Explanation

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.

### Example

A payment call times out; query or safely retry the same idempotent operation instead of creating a second payment.

### Check

The recovery procedure does not equate communication failure with application failure.

### Limits

- Some services cannot reveal a definitive state immediately; preserve the uncertainty instead of inventing certainty.

### Evidence and sources

- supports: 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. — RS-56B6FA675EBAA1EF. The exact state must be checked using the specific service's contract; timeout does not mean either success or failure by itself. (Retry scenarios where the response is lost)
- RS-56B6FA675EBAA1EF: Making retries safe with idempotent APIs — https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/

No review details supplied.
