When a HubSpot workflow does not fire, the cause is almost never the action that did not happen. It is the enrollment that never started. Nearly every "my workflow is broken" problem traces back to one of four things: the trigger criteria, the re-enrollment setting, the timing of when the record met the criteria, or a filter that quietly excludes the record. Here's the practitioner's read on how to find which one it is, in order, without guessing.
Why didn't my record enroll in the first place?
Start with the enrollment trigger, because a record only enters a workflow at the exact moment it newly meets the criteria. The most common mistake is assuming a record that already matches the trigger will enroll. It will not. A trigger like "lifecycle stage is Lead" enrolls a record only when it becomes a Lead, not records that were already Leads when you turned the workflow on. Open the workflow, check the enrollment trigger, and ask a precise question: did this specific record cross that line after the workflow was active? Worked example: you build a workflow to email every contact whose status becomes Marketing Qualified Lead, then wonder why your 2,000 existing MQLs got nothing. They never crossed the line while the workflow was live, only contacts who become an MQL from now on enroll, unless you manually enroll the existing ones or check the box to enroll existing records when you save.
Could a re-enrollment setting be blocking it?
By default a record enrolls in a workflow only once, so a record that already went through cannot go through again unless you allow re-enrollment. If you expect a record to run through the same workflow more than one time, for example a contact who fills out the same form twice, you must turn on re-enrollment and define which triggers allow it. Without that, the second event does nothing because the record has already completed the workflow. Check the re-enrollment tab and confirm both that it is on and that the specific trigger you care about is listed as a re-enrollment trigger. This is the single most common reason a workflow "works the first time and never again."
Is a filter or suppression list quietly excluding the record?
Enrollment can be blocked by goal criteria, suppression lists, or an AND condition the record fails by a single property. Read the trigger criteria literally. If it says lifecycle stage is Lead AND country is United States, a Lead in Canada will never enroll, and that is easy to miss when you skim. Also check whether the workflow has a goal that the record already meets, because a record that already satisfies the goal is held back. And confirm the record is not on a suppression list or unsubscribed if the workflow sends email, since HubSpot will skip the send. Worked example: a contact seemed to vanish from a nurture workflow, the cause was a single missing value, the trigger required a country and the record had none, so the AND condition failed silently.
How do I confirm what actually happened to a record?
Use the workflow's enrollment history and the record's own timeline, because they show exactly when a record entered, where it sits, and why it stopped. Open the workflow, go to the enrollment history or the contact's workflow membership, and look at the specific record. You can see whether it ever enrolled, which step it is paused on, and whether it was unenrolled. On the record itself, the timeline shows workflow events. This turns troubleshooting from a guessing game into a read, you stop theorizing and start looking at what the system recorded. If the record never appears in the history, the problem is enrollment, go back to the trigger. If it enrolled but stalled, the problem is a delay or a branch, follow the path.
The IV-Lead take
Workflow troubleshooting feels mysterious until you accept that the answer is almost always in enrollment, not action. Work the four checks in order, trigger, re-enrollment, filters, then history, and you will find the cause in minutes instead of rebuilding the whole thing. The deeper lesson is that most enrollment bugs are really data bugs, a missing property, an unexpected value, a record that never crossed the line. Clean data makes workflows boringly reliable, and boring is exactly what you want from automation.
Have a workflow that fires for some records and not others? Book a 30-minute portal audit and we will trace it to the root cause with you. For ongoing help, see how we handle HubSpot implementation and optimization.
Frequently asked questions
Why doesn't my workflow enroll contacts that already match the criteria?
Workflows enroll a record at the moment it newly meets the trigger, not records that already match when you activate it. To include existing records, check the option to enroll existing records when you save, or enroll them manually.
Why does my workflow only run once per contact?
By default a record can enroll only once. If you need a contact to run through again, turn on re-enrollment and add the specific trigger as a re-enrollment trigger.
How can I see exactly why a record did or did not enroll?
Check the workflow's enrollment history and the record's timeline. They show whether the record enrolled, which step it is on, and whether it was unenrolled, so you can stop guessing.
Can a suppression list stop enrollment?
Yes. If a workflow sends email, an unsubscribed contact or one on a suppression list will be skipped for the send. Goal criteria the record already meets can also hold it back.
