Connected workflows cannot assume that every request is delivered exactly once. A timeout may hide a successful operation, a queue may redeliver a message, or an operator may retry a task. Idempotency is the practice of designing an operation so that repeating the same intended request does not create an unintended second effect.
Identify actions where duplication matters
Start with operations that create records, send notifications, initiate approvals, move money, change inventory, provision access, or trigger downstream work. A duplicate read is usually harmless; a duplicate state change may not be.
Give each business operation a stable identity
Create an operation or idempotency key before the first attempt and reuse it for retries of that same intent. Store enough state to recognize whether the operation is new, in progress, completed, or failed. Do not generate a fresh identity merely because a transport retry occurs.
Check state before repeating side effects
Where a provider supports idempotency keys or deduplication, use that capability. Otherwise, verify existing state using a stable transaction identifier or application record before sending another external request.
Define the deduplication window
Retention should reflect how long delayed messages and legitimate retries can occur. Document when keys expire and what happens if an old request reappears after that point.
Keep evidence without exposing secrets
Record operation identifiers, attempt timestamps, outcome, and relevant system references. Avoid copying credentials, tokens, or unnecessary sensitive content into logs.
Keep professional decisions separate
Idempotency protects technical execution. It does not authorize an automated system to repeat or override legal, clinical, financial, employment, safety, or other regulated decisions without an appropriately governed process.
Related knowledge
Use this with Automation Retry Design, Automation Exception Queues, Automation Observability, and Automation Handoffs.
References
This is general operational guidance and does not replace system-specific engineering, security, legal, regulatory, or professional review.