# How can a workflow avoid processing the same trigger event twice?

Canonical URL: https://help.iagenify.com/faqs/workflows/how-can-a-workflow-avoid-processing-the-same-trigger-event-twice

[← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)

HELP CENTER · FAQ Workflows 1 min read
# How can a workflow avoid processing the same trigger event twice?
Give each incoming event a stable identifier and check whether that identifier has already been handled before performing side effects. This makes duplicate delivery or a manual retry less likely to create repeated records, messages, or external actions.
IaGenify
Workflows

## Use an event key and a recorded state
A trigger source may deliver the same event again after a timeout or acknowledgement problem. Store an idempotency key or processed-event record in a durable place that later runs can check.
Mark an event as complete only after the intended work is committed. If processing has multiple stages, record stage status so a retry can resume safely instead of treating a partially completed event as new.
## Handle simultaneous deliveries
Two runs may check for the same event at nearly the same time. Use a unique constraint, atomic claim, or other coordination supported by the data store so both do not pass the duplicate check before either records completion.
Test repeated and concurrent delivery with a safe sample and inspect the final state. Keep the event key long enough to cover the source's retry window, and avoid retaining full payloads longer than needed. [← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)