Make Scenario Creates Duplicate Records: How to Find Repeated Executions
When a Make scenario creates duplicate records, the same source event is producing multiple executions or the create module runs without checking for an existing record. The destination fills with duplicates because the scenario creates instead of updating. Distinguish between duplicate input and duplicate processing before changing the destination system.
Table of Contents
- 01.Duplicate input versus duplicate processing
- 02.What to check first
- 03.Is the input duplicated
- 04.Is there a search before create
- 05.Multiple scenarios creating the same record
- 06.Create versus update logic
- 07.How to test it
Duplicate input versus duplicate processing
Duplicates come from two sources. The input itself is duplicated, meaning the source sent the same event twice. Or the processing is duplicated, meaning the scenario runs the create module without checking for an existing record. Duplicate input needs a fix at the source. Duplicate processing needs a search before create. Identify which you have before changing anything.
| Cause | What happens | Fix |
|---|---|---|
| Duplicate input | Source sends the same event twice | Fix the source or deduplicate |
| Missing search | Create runs without checking existing | Add a search module |
| Multiple scenarios | Two scenarios create the same record | Consolidate or guard |
| Repeated webhook | Webhook fires twice for one event | Deduplicate at the trigger |
What to check first
- Check the execution history for repeated runs on the same source event.
- Check whether the scenario has a search module before the create module.
- Check whether multiple scenarios create the same destination record.
- Review the source for duplicate input events.
- Check whether a webhook trigger fired more than once.
Is the input duplicated
Open the execution history and look at the input bundles for the duplicate records. If the same input appears twice, the source sent the event twice. The scenario ran correctly twice and created two records. The fix is at the source, not the scenario. A webhook that fires twice or a source application that sends duplicate events produces duplicate input. This connects to the general webhook duplicate data problem.
Is there a search before create
Without a search module, the scenario creates a record every time it runs. A second run for the same contact creates a duplicate because the scenario never checks whether the record exists. Add a search module before the create module, then branch on whether a record was found. Create only if the search returns nothing, update if it does. This is the single most effective duplicate prevention step in Make.
Multiple scenarios creating the same record
Two scenarios can both create the same destination record. One scenario creates a contact from a form, another creates a contact from a webhook, and both fire for the same person. Neither knows the other exists. List every scenario that creates the destination record type and confirm whether more than one is running. Consolidate them or add a guard that prevents the second from creating when the first already did.
Create versus update logic
The scenario should create when no record exists and update when one does. The pattern is search, then a router that branches on the search result, then create or update. If the scenario always creates, duplicates accumulate. Confirm the scenario follows the search then branch pattern rather than going straight to create.
How to test it
- 1.Trigger the source event once and count the destination records created.
- 2.Check the execution history for repeated runs.
- 3.If the scenario ran once, check whether a search module exists before create.
- 4.List all scenarios that create the same destination record type.
- 5.Check the source for duplicate input events.
- 6.Add a search before create module if one is missing.
Frequently Asked Questions
Why does my Make scenario create duplicate records?
Either the source sent the same event twice or the scenario creates without checking for an existing record. Check the execution history for repeated runs, then add a search module before the create module.
How do I stop my Make scenario from creating duplicates?
Add a search module before the create module, then branch on whether a record was found. Create only if the search returns nothing and update if it does. Also check the source for duplicate input events.
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 Running Twice: Why the Same Workflow May Execute More Than Once
Duplicate execution has two causes that look the same. One workflow running twice needs a different fix than two workflows doing the same action. Identify which you have first.
Automation Is Creating Duplicate CRM Contacts: How to Find the Source
Duplicates come from create versus update logic, not the CRM database. Fix the matching in the workflow before you deduplicate the records.
Webhook Is Sending Duplicate Data: Why the Same Request May Run More Than Once
Duplicate webhooks come from repeated triggers, re-entry, duplicate source events or retries. Trace the source before assuming retries caused the duplicate.