Fix Guides
How to Fix HubSpot Records Not Enrolling in Workflows
A HubSpot record fails to enroll in a workflow when it does not meet the enrollment trigger at the moment it is created or changed, or when a workflow setting (turned off, re-enrollment off, suppression list, goal criteria) keeps it out. It is almost always a configuration gap you can find and fix in a few minutes, not a HubSpot outage.
The Symptom: Why Aren't My Records Enrolling in a HubSpot Workflow?
The workflow is on, you can see contacts, companies or deals that look like they match, and the enrolled count stays flat or the history is empty. Nothing errors. The records simply never show up in the workflow, so the emails, tasks and property updates that depend on it never happen.
Common Causes
- The workflow is not turned on — A draft or paused workflow enrolls nothing. It is the first thing to check and the most often missed.
- The trigger does not match when the record changes — Enrollment is evaluated when a record is created or when a property changes. A record that matches the criteria but never had a qualifying change since the workflow went live does not enroll.
- Existing records were not enrolled at launch — Records that matched before the workflow was turned on are skipped unless you chose to enroll existing records at that moment.
- Re-enrollment is off — A record that already went through the workflow is not enrolled again, even when it meets the trigger a second time.
- A suppression list or another workflow is excluding the record — Records on the workflow's suppression list, or records removed by an unenroll action elsewhere, stay out.
- The record meets the goal criteria — If goal criteria are set and the record already meets them, it is not enrolled, because the goal is treated as already reached.
- Wrong object type or wrong property — A contact-based workflow does not enroll deals or companies, and a trigger built on a property that is empty, renamed or never populated by your forms and integrations never fires.
How to Fix It — Step by Step
- 1. Confirm the workflow is on. Open the workflow and check its status. Turn it on if it is a draft or paused.
- 2. Check the object type and the trigger. Make sure the workflow is built on the same object as the records you expect (contact, company, deal, ticket) and that the trigger filters match the real property values on a record that should have enrolled.
- 3. Look at the record, not the workflow. Open a record that should have enrolled and look at its activity and workflow history. Then open the workflow's History tab and search for the record. If it appears there as not enrolled, the reason is usually shown. If it does not appear at all, the trigger never evaluated it.
- 4. Decide how existing records should be handled. If the records matched before the workflow went live, edit the enrollment settings to enroll existing records, or run a one-time import or list-based enrollment for the backlog.
- 5. Turn on re-enrollment where it is intended. If a record should go through the workflow every time it meets the trigger, enable re-enrollment and pick the properties that allow it.
- 6. Review suppression lists and unenroll actions. Check the workflow's suppression list, then search your other workflows for unenroll actions that could be removing the same records.
- 7. Review the goal criteria. If the goal is already true for the records you expect, they will not enroll. Loosen or remove the goal, or accept that the records are done.
Prevention
- Decide on existing records when you launch a workflow, so the backlog is enrolled on purpose instead of discovered later.
- Set re-enrollment deliberately for every workflow instead of leaving the default.
- Keep a short list of suppression lists and unenroll actions so a new workflow does not collide with an old one.
- Test with a record that should enroll before you rely on the workflow, and check its history afterwards.
- Audit active workflows on a schedule. Settings drift as properties are renamed and teams change.
This Problem Is Rarely Limited to One Workflow
If one workflow has a trigger gap or a missing re-enrollment setting, others built the same way usually do too. Run Wrenk's free health check to find every instance of this in your org, not just the workflow that just caught your attention.
Related Guides
- Workflow rule deprecation — inventory, classify and migrate legacy automation.
- Continuous health checks — review automation settings across the portal.
FAQ
Why aren't my records enrolling in a HubSpot workflow?
Almost always one of a few things: the workflow is not turned on, the record does not match the enrollment trigger at the moment it changes, the record has already been through the workflow and re-enrollment is off, the record sits on a suppression list, or it meets the goal criteria. Work through them in that order.
Why did existing records not enroll when I turned the workflow on?
A workflow with filter-based triggers enrolls records as they are created or updated to match. Records that already matched before you turned it on are only enrolled if you chose to enroll existing records when you set the workflow live. If you did not, only new changes enroll.
A record matches my trigger. Why did it enroll once and never again?
Re-enrollment is off by default, so a record that has been through the workflow once will not enroll a second time. Turn on re-enrollment and choose which property changes should allow it.
Can another workflow stop a record from enrolling?
Yes. An 'unenroll from workflow' action in another workflow, or a suppression list on this one, will keep a record out even though it matches the trigger. Check both before changing the trigger.
How do I find every workflow with this problem?
Open each active workflow and compare its trigger, re-enrollment, suppression and goal settings against what you expect. In a portal with many workflows that is slow, and it is the part a health check does for you across the whole portal.
Wrenk finds and fixes this across your whole org as part of managed Salesforce operations.