How to Stop an Automation Sending Twice (or Too Late)
How to stop an automation sending twice: decide re-entry on purpose, give every workflow an exit goal, and make sure no two workflows message the same person.
How to stop an automation sending twice: set a deliberate re-entry rule so a person already inside a workflow cannot be enrolled again, give every workflow a goal that removes people, and check that no other workflow messages the same person at the same moment.
How to stop an automation sending twice
It happens like this. Someone fills in your form. Later, because they forgot something or because two events fired, they fill it in again. Your workflow sees a new trigger. They are enrolled a second time. Now they get every message twice.
It is the most common automated embarrassment there is. And it is entirely preventable.
Here is what a duplicate says to the person receiving it: nobody is paying attention. That is a precise message, and the opposite of the one you built the workflow to send. A repeated email feels worse than a missing one, because a missing one is invisible.
The fix is a rule, made on purpose, for each workflow. Not a setting you leave at whatever the tool defaulted to.
The default: nobody enters twice
Start from this. By default, a person who is already inside a workflow should not be enrolled in it again.
Start there, and allow exceptions only where they are clearly intended. The classic exception is a workflow that should genuinely run each time something recurs, such as every time a customer renews. A renewal reminder that fires once and never again would be a bug of its own.
So the question is never "should repeats be allowed?" in general. It is "for this workflow, what should happen if the same person triggers it again?" There are really only three answers:
- Ignore the second trigger. Right for onboarding, welcome messages and anything meant to happen once per person.
- Let them back in after they have left. Right where the event genuinely recurs and the first run has finished.
- Let them in again, with a different path. Right where a repeat means something, such as a returning enquirer who deserves a task for you rather than a second confirmation.
Write the answer next to the one-line note of what the workflow is for. You will want it when you review the workflow later.
Free guide · 21 pagesAutomate the follow-through, not the relationship.The Automation Playbook: what to hand to a machine first and how to build it so it behaves.Get the free guide →Where doubles actually come from
Knowing the causes helps you spot them. Here is the short diagnostic.
| What the person sees | Likely cause | The fix |
|---|---|---|
| The same message arrives twice, close together | Two events fired and enrolled them twice | Block re-entry while they are inside |
| The whole sequence arrives a second time, weeks later | They filled in a form again and re-entered after finishing | Decide on purpose whether a repeat should restart it |
| Two different messages with the same purpose | Two workflows both react to the same event | Check that no other workflow sends a conflicting message at the same moment |
| "Are you still interested?" after they bought | No goal removes them when they convert | Add the goal that ends the workflow |
| A reminder to book a call after they booked | The workflow never checked the situation had changed | Stop it on the goal, whatever step they are on |
| Still receiving messages after they opted out | No check before the send | Check opt-out before every send, in every workflow |
Notice that only the first three rows are duplicates in the strict sense. The rest are cousins of an automation sending twice. They all give the same result: your automation keeps talking after the conversation has moved on.
Staleness: the other kind of automation sending twice
A message can be a duplicate in spirit even if it is sent once. The follow-up that arrives after someone bought. The reminder to book to someone who booked yesterday. It repeats what they have already done, and it announces that nobody was listening.
This is the exit rule from the design stage, enforced. Every workflow that sends over time should be stopped by the goal it exists to achieve. If the person reaches the goal, they leave, whatever step they were on.
That is why a good workflow has two written lines before it has any steps: what starts it, and what ends it. Design the end at the same time as the start. If you want the full method for that, how to design a workflow trigger condition action walks the sentence version.
Then ask the wait question: what should happen if the situation has changed while they were waiting? A pause between steps is the perfect hiding place for a stale message. The person converts during the wait, and the next step fires regardless. Build the check in, or end the workflow on the goal.
Workflows that talk over each other
Single workflows get all the attention. The problem is often between two.
You build a welcome sequence. Later you build a follow-up for new leads. A new person qualifies for both. They receive a welcome and a "just checking in" on the same afternoon, with different tones, possibly contradicting each other. Neither workflow is wrong. The overlap is.
Before you switch anything on, ask: could this person already be inside another workflow right now? What would that one say? If the answer is yes and the messages conflict, narrow one of the entry rules, or have one workflow end the other when a person qualifies.
This is also a quiet argument for keeping the number of workflows small. You can hold a handful in your head. You cannot hold dozens, and nobody else will. The more you run, the more overlaps you create without noticing.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →The off switch your recipients hold
One kind of repeat is not merely embarrassing. It is a breach.
Anyone who receives your marketing messages must be able to stop receiving them, easily, and you must honour it without exception. That means a working unsubscribe on every marketing message, and a check before every send. Including sends from workflows that were built before the person opted out.
That last part is where it goes wrong. You built the workflow in spring. The person unsubscribed in summer. The workflow does not know unless the check happens at send time. In many places getting this wrong is unlawful, and it damages your ability to reach everyone else.
Treat this as the one non-negotiable item on the list. If you are choosing what to keep a human on, what a solopreneur should never automate includes the moments where a repeat message does the most damage.
Why a duplicate costs more than it looks
It is tempting to shrug. Two emails, so what. But think about who it hits.
It hits the people who responded. The ones who filled in your form are your warmest contacts, and the form is the trigger. A repeat lands on them first. They did something, and what they got back was proof that your system was not watching.
It also hits at scale. One person receiving a double is a nuisance. A trigger that double-enrols is doing it to everyone who meets it, quietly, every day, until you look. You will not get a complaint for most of them. People do not write in. They just trust you a little less.
That is why this belongs in your weekly look at what the workflows actually did. If entries are higher than the number of people who really arrived, something is enrolling twice. If the numbers surprise you, there is almost always a reason worth finding.
Free guide · 21 pagesAutomate the follow-through, not the relationship.The Automation Playbook: what to hand to a machine first and how to build it so it behaves.Get the free guide →Check it before it goes live
You will not catch every duplicate by thinking. You catch them by testing on yourself.
Run the workflow end to end on a contact you control. Then trigger it a second time, the way a real person would. Does it enrol you again? Do you get everything twice? Does the second pass do what you decided it should? Be aware that in many tools a test is a real run, which is exactly why that contact should be you.
Then read the records. Check how many people entered, how many reached each step and how many finished. A count that looks too high is a clue. And once the workflow is live, look at a sample of the messages that went out. How to test an automation before it goes live gives the full routine.
Last, a checklist of five lines before you switch on:
- Have I decided, on purpose, whether a person can enter more than once?
- Is there a goal that removes the person, whatever step they are on?
- Do the waits account for the situation changing?
- Does any other workflow send this person a conflicting message at the same moment?
- Does every marketing message carry a working way to stop, and is it checked before each send?
Five boxes. Tick them honestly or do not switch it on.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
Why did a customer get the same email twice?
Usually two events fired for the same person, or they filled in a form again, and the workflow enrolled them a second time. Block re-entry while someone is inside a workflow, and decide on purpose when a repeat should be allowed.
Should I ever allow people to re-enter a workflow?
Yes, where the event genuinely recurs, such as a renewal. Make that a deliberate choice for that workflow rather than a tool default.
How do I stop messages arriving after someone has bought?
Give the workflow a goal that removes people when they reach it. Anyone who converts leaves immediately, whichever step they were on, and the next message never fires.
What if two of my workflows contact the same person?
Check for overlap before switching anything on. Narrow the entry rules, or let one workflow end the other when a person qualifies. Fewer workflows make an automation sending twice easier to see.
The full method, with the checklists, is in The Automation Playbook, a free 21-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.