HubSpot workflows that do not misfire
Most HubSpot workflow failures come from four causes: enrolment criteria that can never be met, re-enrolment left off when it was needed, two workflows writing the same property so the last one wins, and no suppression list so contacts already in a sales conversation receive marketing sequences.
By HubReven
A workflow is an if this then that rule that runs on a schedule you do not control, against records you cannot see all of, for as long as nobody turns it off.
That is why they go wrong quietly. Here is how they actually behave and the four ways they break.
Enrolment is the whole design
Everything hangs on one question: which records enter this workflow.
Enrolment triggers define entry. A contact enters when it first matches the criteria.
The most common mistake is criteria that can never be true. "Lifecycle stage is MQL AND form submission is X" fails silently if lifecycle updates only after a nightly sync, because at the moment the form fires the record is still a Lead. Nobody enrols, nobody notices, and six months later someone asks why the workflow has zero enrolments.
Check the enrolment count after 48 hours. A workflow that enrolled nobody is telling you the criteria are wrong, not that nobody qualified.
Re-enrolment, the setting everyone forgets in both directions
By default a contact enters a workflow once, ever. Re-enrolment lets them enter again when they match the trigger anew.
Leaving it off when you needed it on: a customer who requests a demo in March and again in September only ever gets the first follow up. The second request vanishes.
Turning it on when you needed it off: a welcome sequence that re-enrols every time a property changes emails the same person the same welcome four times.
The rule: turn it on for behavioural triggers that recur, such as a form submission or a page visit. Leave it off for lifecycle milestones that should only happen once.
Suppression, the thing that prevents embarrassment
The failure that gets noticed by customers rather than by admins.
A contact is deep in a negotiation with a sales rep. A marketing workflow does not know that, so it sends a "still thinking about us?" email. The rep finds out from the prospect.
Every marketing workflow needs an exclusion list. At minimum: contacts with an open deal, current customers, unsubscribed contacts, and anyone already enrolled in a competing sequence. Build it once as a shared active list and reference it from every workflow rather than rebuilding the criteria each time.
The four failure modes
1. Criteria that cannot be met. Covered above. Symptom: zero enrolments.
2. Two workflows writing the same property. Both fire, last one wins, and the result depends on timing rather than intent. Symptom: a property that changes back and forth.
The fix is ownership. One workflow owns lifecycle stage. One owns owner assignment. If two need to write the same field, merge them.
3. Delays that outlive their reason. A three day delay then "send follow up" keeps sending after the deal closed. Add a goal, or a condition before the send that re-checks the state.
4. Unenrolment that never happens. Contacts pile up inside a long workflow for months. Set goals so they exit when the purpose is met, and check the currently enrolled count occasionally. A number that only grows is a problem.
Before you build anything
Three questions, answered in writing:
- Who should enter, and can the system actually tell? If the criterion depends on data that arrives late, the trigger is wrong.
- What ends this? The goal, and what happens to people who never reach it.
- Who owns each property this writes? If the answer is more than one workflow, stop.
Audit what you already have
If there is a portal full of workflows nobody remembers building, do this before adding more:
- List active workflows sorted by last enrolment date. Anything with zero in 90 days is a candidate for deletion.
- For each active one, note which properties it writes. Overlaps are your conflicts.
- Check currently enrolled counts. Large and growing means people are not exiting.
- Confirm every marketing workflow references the suppression list.
That inspection is one of the six areas in a portal audit, and it is usually where the surprises are. If the underlying problem is that the data those workflows depend on is unreliable, the fix is upstream of automation entirely.
Frequently asked questions
Why is my HubSpot workflow not enrolling anyone?
Almost always enrolment criteria that cannot be true at the moment the trigger evaluates, usually because one of the conditions depends on a property that updates later. Test with a single record that you know should qualify.
What does re-enrolment do in HubSpot?
It lets a contact enter the same workflow more than once when they match the trigger again. Turn it on for behaviours that recur like form submissions, and leave it off for one time lifecycle milestones.
How do I stop workflows emailing contacts who are already talking to sales?
Build one shared active list of contacts to exclude, covering open deals, customers and unsubscribes, and reference it as a suppression list from every marketing workflow rather than recreating the criteria each time.
How many workflows is too many?
There is no count, but overlapping ones are the real problem. If two workflows write the same property, you have a conflict whose outcome depends on timing. Merge them or assign clear ownership per property.
Get the next one