Automation Running Twice: Why the Same Workflow May Execute More Than Once
When an automation runs twice, the same workflow executes more than once for what should be one event. The cause is either one workflow running twice or two different automations performing the same action. Distinguish between the two before removing anything, because the fix is completely different.
Table of Contents
- 01.Two different causes that look the same
- 02.What to check first
- 03.One workflow running twice
- 04.Two different workflows
- 05.Repeated source events
- 06.Re-entry and duplicate records
- 07.How to test it
Two different causes that look the same
Duplicate execution has two distinct causes that produce the same symptom. The first is one workflow running twice for a single event, usually caused by duplicate triggers, multiple entry points or workflow re-entry. The second is two different automations performing the same action, where each workflow runs once but both do the same thing. The fix for the first is to stop the duplicate run. The fix for the second is to remove or differentiate one of the workflows. Diagnosing the wrong cause wastes time, so identify which one you have first.
| Cause | What happens | How to confirm |
|---|---|---|
| Duplicate triggers | One workflow fires twice | Two trigger entries in history |
| Multiple entry points | Same workflow entered twice | Multiple enrollment records |
| Workflow re-entry | Contact re-enters after completion | Re-entry enabled, repeated event |
| Two separate workflows | Two automations do same action | Two different workflow logs |
| Repeated source event | Source fired twice | Two source events in source log |
What to check first
- Check the workflow history and count how many times the workflow ran for the contact.
- If it ran once, check whether a second workflow performed the same action.
- If it ran twice, check for duplicate triggers or multiple entry points.
- Check the source event log to see if the source fired more than once.
- Confirm whether re-entry is enabled on the workflow.
One workflow running twice
If the same workflow ran twice for one contact, the trigger fired twice or the contact entered twice. Duplicate triggers happen when the same event is configured as a trigger in two places, or when a trigger and a manual action both start the workflow. Multiple entry points happen when the workflow can be entered from more than one path. Check the enrollment history. Two enrollment records for the same workflow on the same contact means the entry happened twice. The fix is to remove the duplicate trigger or restrict entry to one path.
Two different workflows
If the workflow ran once but the action still happened twice, a second workflow performed the same action. This is common when similar workflows are built over time and both trigger on the same event. Check whether another workflow exists that sends the same email, adds the same tag or creates the same record. Each workflow runs once, but the combined effect is a duplicate. The fix is to disable or differentiate one workflow, not to change the trigger. Duplicate messages from this pattern are covered in the guide on automation sending duplicate emails or SMS.
Repeated source events
Sometimes the source event itself fired twice. A form submitted twice, a webhook sent twice or a contact was imported twice. Each source event legitimately triggers the workflow, so the workflow runs correctly twice. The fix is at the source, not the workflow. Check the source system log to see whether the event occurred twice. Webhook retries can cause this, and the guide on webhook sending duplicate data covers that path.
Re-entry and duplicate records
Re-entry allows a contact to enter the same workflow again after completing it. If re-entry is enabled and the trigger fires again, the contact starts a new run while the old one is finished. This is legitimate behavior, but it can look like a duplicate if you did not intend re-entry. Duplicate contact records can also cause two runs because the platform sees two different contacts. Re-entry is covered in the guide on automation workflow re-entry problems.
How to test it
- 1.Trigger the event once and check how many times the workflow runs.
- 2.Count the enrollment records for that contact in that workflow.
- 3.If the count is two, check for duplicate triggers or multiple entry points.
- 4.If the count is one, search for a second workflow performing the same action.
- 5.Check the source event log to confirm the source fired only once.
Frequently Asked Questions
Why is my automation running twice for one event?
Either one workflow is firing twice due to duplicate triggers or re-entry, or two separate workflows are performing the same action. Check the workflow history to count the runs, then check for a second workflow doing the same thing.
How do I stop an automation from running twice?
First confirm the cause. Remove duplicate triggers if one workflow runs twice, or disable one of the workflows if two separate automations perform the same action. Check the source event log to rule out the source firing twice.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Automation Sending Duplicate Emails or SMS: How to Find the Duplicate Path
Duplicate messages come from one action running twice or multiple paths sending the same content. Map every message path before removing any workflow.
Automation Re-Entry Problems: Why the Same Contact Keeps Entering the Workflow
Re-entry may be legitimate or unwanted. Check the enrollment count, the re-entry setting and the trigger count before deciding whether to block repeated entry.
Marketing Automation Workflow Not Triggering: What to Check First
A workflow that never starts usually breaks between the business event and the first action. Trace the flow from trigger to conditions to entry to find where the workflow fails to start.