# Treat a timeout as an unknown outcome before repeating the action

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 before repeating the action

ID: MHC-D-RESEARCH-0975 · Version: 0.1.0 · Kind: pattern
Source: https://vedokrok.com/knowledge/treat-a-timeout-as-an-unknown-outcome-before-repeating-the-action

No reply is not the same as no action.

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

### Use when

- A send, create or update request times out after leaving your application.

### Avoid when

- Reconciliation against stale or incomplete data can also mislead. Do not invent an automatic retry rule for an undocumented interface.

### Explanation

The receiver may have completed the operation while its response was lost. Preserve an unknown or pending state and reconcile using the operation's identity before creating a fresh request. Where a documented idempotent retry is available, follow that contract.

### Recognition

No reply is not the same as no action.

### Example

An import request times out. Its run identifier reveals that the job is already processing, so a second import is not started.

### Check

The status distinguishes confirmed failure from an unconfirmed outcome.

### Limits

- Reconciliation against stale or incomplete data can also mislead. Do not invent an automatic retry rule for an undocumented interface.

### Evidence and sources

- supports: A request that receives no response may already have created its intended resource; blindly retrying can create additional effects. — RS-ABFC60C5149B88E0. Reconciliation requires an authoritative receiver view and enough identity information to distinguish this operation from another. (Retrying and side effects)
- RS-ABFC60C5149B88E0: Making retries safe with idempotent APIs — https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/reuse-the-operation-identity-when-retrying-the-same-intent
