Help centre / Workflows and automation

HubSpot workflow not triggering? Why records don't enroll and how to fix it

Why a HubSpot workflow doesn't enroll records, how to check each cause, and how to enroll the records it missed.

By Abdur Rahim Mostafa, HubSpot consultant · Updated 26 October 2026 · 5 min read

A HubSpot workflow that "isn't triggering" is usually doing what its settings tell it to do. The record already went through once and re-enrollment is off, or it met the trigger before the workflow was switched on, or a suppression segment or unenrollment rule took it out straight away. Less often, the trigger logic doesn't match the record in the way you expect.

Start with HubSpot's own check. Open the workflow, click Help, then Troubleshoot enrollment, and choose a record that should have enrolled along with a date and time range. It covers property, list and form submission filters. For other triggers, click the enrollment trigger box and use the Test option in the left panel to see which filters the record meets and which it fails.

Why a HubSpot workflow doesn't enroll records

The workflow is off, or built on the wrong object

Only workflows that are turned on enroll records. To switch one on, click Review and publish, then Turn on. Check the object type too. A deal-based workflow enrolls deals, so a contact that matches your filters will never appear in it. The workflows tool needs a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub, as of October 2026 (HubSpot's enrollment troubleshooting article lists the plans).

The record met the trigger before the workflow went live

When you turn on a workflow with filter triggers, HubSpot asks whether to enroll records that already meet the criteria. If someone chose to only enroll records that meet them after the workflow is turned on, every record that already matched was left out.

Event triggers work this way by design. They only react to events after the workflow is on, and the record has to exist when the event happens, so activity from before someone became a contact doesn't count (event triggers). A list membership trigger fires when a record joins the list, so records already in the list when you switched on have to be enrolled by hand.

It went through once already

By default a record enrolls the first time it meets the triggers and never again. That matters when you test with the same contact more than once. In the workflow editor, click View, then Enrollment history, and search for the record. If it's there, you need re-enrollment triggers, covered in why records don't re-enroll. A record still active in the workflow, for example waiting in a long delay, can't enroll a second time either.

A suppression segment, goal or unenrollment rule removed it

Click the enrollment trigger and open the Settings tab. In contact-based workflows this holds suppression segments, goals and the option to unenroll contacts who no longer meet the conditions. A contact in a suppression segment is never enrolled, can't be enrolled by hand, and removing them from the segment later doesn't enroll them. In company, deal, ticket and other workflows the same tab holds unenrollment triggers, and a record that already meets them is kept out from the start.

Then look at your other workflows. One with Unenroll contacts from other workflows when enrolled in this workflow switched on can pull a contact out of yours the moment it enrolls there.

The trigger logic doesn't say what you meant

A record only needs to match one group of triggers, and inside a group it has to match every filter. The test panel puts a tick or a cross next to each filter, so the failing one is easy to spot. Three kinds of filter catch people out.

  • Empty values. Company, deal, ticket and custom object workflows leave out records where the property is empty unless you tick Include records where [property name] is empty.
  • Relative dates. Filters such as "is more than 30 days ago" are checked at the start of each day, so a record can qualify hours before it enrolls.
  • Event refinements. Extra filters on an event trigger are checked once, when the event happens. If the contact's lifecycle stage was wrong when they submitted the form, fixing it afterwards won't enroll them.

It enrolled, but nothing seems to happen

Sometimes the record is in and the first action is waiting. Run actions at specific times in workflow settings holds actions until the next allowed slot. See workflow delays and timing for that.

How to fix a workflow that isn't enrolling

  1. Confirm the workflow is on and built on the object you expect.
  2. Pick one record that should have enrolled and run Troubleshoot enrollment on it.
  3. Test the same record against the triggers and note any filter with a cross.
  4. Search the enrollment history to see whether the record enrolled before, or enrolled and was removed.
  5. Check the trigger's Settings tab for suppression segments, goals and unenrollment rules.
  6. Fix the trigger or setting. If you edit triggers on a live workflow, decide on purpose whether records that already match should enroll.
  7. Enroll the records that were missed. Click Enroll in the workflow and choose a filter, a list or individual records. Records that already went through are skipped unless re-enrollment is on (manual enrollment).
  8. Watch the next real record go through before you call it fixed.

How to stop it happening again

Treat the "enroll existing records?" prompt as a real decision every time you turn a workflow on or change its triggers, and write your answer in the workflow description. Test with a record that has never been through the workflow. On Enterprise, the workflow settings can email you when the enrollment rate rises or drops past a level you set, which catches a trigger that quietly stops firing. To check a whole portal, my HubSpot audit checklist starts with workflows.

From client work

At PICO IV, after a form change, every website signup for one brand went to the same default rep, whichever rep the provider had chosen. The form and the routing workflow were using different fields. I changed the routing to read the field the form writes. Read the PICO IV case study.

In a workflow audit for Conference Badge I found four workflows failing silently and fixed all four. Read the Conference Badge case study.

If you'd rather have someone go through your workflows with you, I can audit and fix them.

Questions

Why won't my test contact go through the workflow again?

Records enroll once by default. Turn on re-enrollment for the right trigger, or test with a record that has never been enrolled.

Can I enroll records that met the trigger before the workflow was on?

Yes. Click Enroll in the workflow and pick a filter, a list or individual records. Manual enrollment skips the trigger check. Records in the suppression segment or meeting the unenrollment rules still stay out.

Does the Test option run the actions?

No. It simulates the path and shows when each action would run. Only Send preview does something real, and it sends the emails on that path to your own address.

How far back can I check enrollments?

HubSpot keeps enrollment history for six months and action logs for 90 days.

Did this fix it?

Written by Abdur Rahim Mostafa. I'm an independent HubSpot consultant with 12 years of HubSpot work. I fix and build HubSpot portals, integrations and automation for teams in the US, UK and Australia. See my case studies or find me on LinkedIn.

Can't find your fix?

Book a free 30-minute call and show me what's happening in your portal. If it needs work, you get a written scope and one fixed price.

Book a free 30-minute call