# Give a retryable mutation one stable operation ID

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
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Give a retryable mutation one stable operation ID

ID: MHC-D-RESEARCH-0347 · Version: 0.1.0 · Kind: pattern
Source: https://vedokrok.com/knowledge/give-a-retryable-mutation-one-stable-operation-id

A retry should mean 'finish this operation,' not 'please create another one.'

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

### Use when

- A create or update request may be retried after a timeout, dropped connection or transient service error.

### Avoid when

- Do not assume idempotency exists where the service does not guarantee it, and do not reuse one key for materially different requests.

### Explanation

Attach a stable idempotency or request key to one logical mutation and reuse it for retries of that same intent. Generate a new key only for a genuinely new operation. Store enough context to recognize ambiguous responses and reconcile them. This is especially valuable for payments, job creation, provisioning and bulk actions where duplicates are expensive.

### Recognition

A retry should mean 'finish this operation,' not 'please create another one.'

### Example

If a create-order call times out, retry with the same operation ID rather than issuing a second independent create request.

### Check

Repeated delivery of the same logical request cannot silently create multiple intended-once effects under the API contract.

### Limits

- Do not assume idempotency exists where the service does not guarantee it, and do not reuse one key for materially different requests.

### Evidence and sources

- supports: Amazon and Stripe document idempotency keys or request identifiers as a way to safely retry a mutation without unintentionally performing the same logical operation twice. — RS-56B6FA675EBAA1EF. Idempotency semantics depend on the API contract and retention window; callers must not assume every endpoint supports them. (Client request identifiers and retry safety)
- RS-56B6FA675EBAA1EF: Making retries safe with idempotent APIs — https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/

### Vedokrok editorial review

Keep the operation key within its contract

Reuse one key for retries of the same intended change. First check what the API promises: a repeated key only helps when the service still recognizes it.

#### Keep identity and intent together

Store the key with the request parameters and result or unresolved status. Retry with that same identity after an ambiguous response; do not silently generate a second create request. Give a genuinely new operation a new key, and never reuse a key for changed parameters. Check which endpoint, account or other scope the service uses to recognize duplicates.

#### Check the lifetime before replay

Find the service's retention rule and what happens after it expires. Stripe, for example, may treat reuse of a pruned key as a new request; it also returns saved failures for recognized retries. A stable key therefore does not promise eventual success or indefinite duplicate protection. If recognition is uncertain, reconcile the original outcome before deciding whether to issue another mutation.

**Editorial takeaway:** For one timed-out request, locate its saved key and parameters, verify the service's recognition window, and choose a same-operation retry or an authoritative status check.

#### Editorial evidence

- supports: Amazon describes caller-provided request identifiers and parameter checks to distinguish a retry from a different intent. — RS-56B6FA675EBAA1EF. Selected official passages read on 2026-10-04. This is an API contract pattern, not a guarantee for endpoints that do not implement it. (Reducing client complexity; Same client request ID, different intent)
- limits: Retention requirements for recognizing earlier requests vary by service and resource. — RS-56B6FA675EBAA1EF. Selected official passages read on 2026-10-04. The card does not transfer EC2 retention semantics to other APIs. (Late arriving requests and the life span of unique client request identifiers)
- limits: Stripe returns a stored result for a recognized key, including failures, and may create a new request after the original key is pruned. — RS-BB8881D82498DEB5. Official API page selected passages read on 2026-10-04. Stripe-specific behavior is an example; readers must inspect the contract of their own endpoint. (Idempotent requests: saved results, key pruning and parameter comparison)
- RS-56B6FA675EBAA1EF: Making retries safe with idempotent APIs — https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/
- RS-BB8881D82498DEB5: Idempotent requests — https://docs.stripe.com/api/idempotent_requests

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/treat-a-timeout-as-an-unknown-outcome
