Duplicate Events and Delivery Failures
Event senders can deliver an event more than once, especially after a timeout. Design event-driven workflows to recognize repeated deliveries.

Illustrative application logic. Use a durable, atomic event ledger and provider-supported idempotency where available. Recovery must reconcile interrupted operations; a missing completion marker does not prove the external write failed.
Before you begin
A stable event ID or business identifier from the sender.
Key concepts
Event ID
An identifier for a delivered event. Use it to recognize duplicates where the sender guarantees stable event identifiers.
Idempotency
A contract under which repeating the same intended operation does not create an additional change. Use it only where the provider or public operation explicitly supports it.
Retry
A repeated attempt after a failed or uncertain operation. It can repeat external changes; use it only when the result is understood.
Side effect
A change outside the returned answer, such as creating a record or sending email. Cancellation or release rollback does not undo a completed side effect.
Reconciliation
Checking the run or destination to determine whether an uncertain operation completed. Do this before retrying a write after a timeout.
Handle duplicate events
Keep the event identifier with the workflow input.
Check whether the corresponding business operation has already completed before writing again.
Inspect delivery history and run history together when an event is missing or repeated.
Repeated delivery does not unintentionally repeat the business operation.
Behavior and limitations
Do not assume exactly-once delivery. A sender can retry even when the first workflow is still running. A failed delivery response does not establish that no external change occurred. Use provider-supported idempotency controls where available and preserve external record IDs for reconciliation.
Related resources
Was this helpful?

