Why an automation runs twice, and what to do

Short answer. When an automation does something twice, find out first whether it ran twice or ran once and created two records. Then look for one of five causes: a trigger that picks up more than it should, two automations sharing a trigger, an automation that triggers itself, a replay after a timeout, or the sending app delivering extra or repeated events. The fix depends on which one it is, so diagnose before you change anything.

This guide rests on Zapier’s own help article for the first four causes and on community reports for the fifth. Community threads are users’ experience, not vendor documentation, and we label them as such. We have not run these tools ourselves.

Step 1: pause it and gather evidence

1. Turn the automation off while you investigate, especially if it sends messages to customers.
2. Open the run history. Search for a value that appears on both records, such as an order ID or an email address.
3. Compare the two runs. Are the inputs identical, or different?
4. Count the runs. One run with two records points at the action. Two runs with the same input point at the trigger or the sender.

Step 2: match the pattern

What you see	Plausible cause	Simplest next step
Two runs, same input, seconds apart	The sending app sent more than one event, or several event types, to the same webhook (reported by community users on Make)	Limit the sender to the one event you need, check the sender’s own log, and store a unique ID so repeats are skipped
Two runs, different automations, same trigger	Multiple automations use the same trigger (Zapier’s article lists this)	Add a filter to one, or merge them into one automation with branches
Runs keep coming, each creating data that starts the next	The automation writes to the same place it watches (Zapier calls this an unintentional loop)	Change where it writes, or filter out records the automation created
Many runs from one change	Trigger settings are too broad	Narrow the trigger, or filter in the source app or with a filter step
One run, two records	The create step ran twice, or an errored step was replayed after a timeout	Check whether the record exists before replaying an errored step. Use a “find, or create if not found” action
Test text appears in real records	A fixed value was left in a field instead of a mapped one (Zapier lists this)	Map the field to dynamic data from the earlier step

If none of these fit, send the vendor’s support links to the duplicating runs and full-page screenshots, as Zapier’s article advises.

Step 3: put a stop in the path for customer messages

A duplicate record is annoying. A duplicate message to a customer is public. For anything that sends email, chat or invoices:

• Add a human approval step before the send, until you trust the automation.
• Record an ID for every message sent and check it before sending again.
• Test with one invented record that you control, never a live customer.
• Set a daily cap where the tool supports one, and read the tool’s behaviour at its limit.
• Keep a way to stop it that you can reach from a phone.

See the illustrative follow-up workflow for an approval-first design.

Before you turn it back on

Use one invented record with a unique ID and observe its complete path: trigger, filter, action and any message sent. Confirm that one input created one run and one expected record. Then turn the automation on for a small, monitored batch before restoring normal volume. If your tool charges by task, credit or execution, estimate the trial’s usage first with our billing-unit guide.

What duplicates cost

Metered tools count each action. Zapier counts tasks, Make says most actions use one credit, and Lindy draws on pooled credits. A runaway or duplicate automation can burn an allowance quickly and, on some plans, trigger extra charges. Read how automation tools bill their usage and check the plan’s behaviour at its limit before you leave anything running unattended.

What we have not verified

We read Zapier’s article only. We have not found official Make documentation on duplicate runs, and we have not researched n8n or Lindy’s duplicate handling. Sequential processing and data stores are suggested in community threads; one user there reported that sequential processing did not remove the duplicates. Check the vendor’s current documentation before relying on a setting.

Sources and dates

Zapier Help, Zap is creating duplicate data, read 21 October 2026. Community reports (not vendor documentation) on Make’s forum, both opened on 21 October 2026: webhook triggering multiple times, where causes and fixes concern what the sender posts, and scenario running twice, which suggests deduplicating with a data store and a unique ID. Billing facts from the vendors’ pricing pages as recorded on the tool pages.