Protocol
Reuse the operation identity when retrying the same intent
A retry should not introduce itself as a brand-new business request.
Before you use it
- Use when
- An interface supports idempotency and transient failures require retries.
Keep this limit in mind
- A token field alone does nothing unless the receiver enforces it. Expired keys, changed scope and partially completed workflows need explicit handling.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
An idempotency key identifies one intended operation, not merely a network attempt. Retain that key when retrying the same operation under the receiver's documented rules. A genuinely new intent needs its own identity, even when its payload happens to look identical.
Steps
- Confirm that this operation implements deduplication and read its scope and retention rules.
- Store the operation key with the original parameters before sending.
- Reuse the key for permitted retries; reject accidental parameter changes instead of silently reusing it.
An example
Retrying one account-creation request preserves its key. Creating a second account deliberately uses a different key.
Check your result
A controlled retry test produces one intended effect, and a separate intent remains possible.
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 readingReuse the operation identity when retrying the same intent
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaTreat a timeout as an unknown outcome before repeating the action
Evidence and sources
Supported EC2 operations use client tokens to recognize repeated requests, with operation-specific scope and parameter rules.
Adding a token to an arbitrary request has no protective effect unless the receiver implements the corresponding contract.
Ensuring idempotency in Amazon EC2 API requests · Client tokens; Types of idempotency
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.