A HubSpot workflow stopped enrolling contacts and there is no error. Here is how to find out why.

This is one of the more frustrating things that can happen in HubSpot. A workflow that ran fine for months suddenly enrolls nobody. The workflow is still switched on. There is no red banner, no failed action, no email from HubSpot. The performance chart simply flattens out.

The reason it is invisible is that nothing technically failed. A workflow enrolls contacts when they match its trigger. If the trigger stops matching anyone, the workflow has nothing to do, so it does nothing. That is not an error condition, so nothing gets reported. The real failure lives one level upstream, usually in a property, a form, a list or an integration, and you have to go and look for it.

Below is a checklist of the causes that actually come up. Work through it in order. Most cases are found in the first four.

The diagnostic checklist

1. A form field was renamed or deleted, so the enrollment trigger no longer matches.
   If your trigger is a form submission combined with a field value, or "property is known", start with the form itself. Open Marketing → Forms, open the form, and compare its fields against what the workflow expects. A field removed during a redesign stops writing the property the workflow watches. Then open the workflow, click the enrollment trigger, and look for a field reference that is greyed out or shows a name you no longer recognise.
2. A property was merged, or its internal name changed during a cleanup.
   Go to Settings → Properties, find the property used in the trigger, and open it. Check the internal name, not the label. The label can be edited freely, but the internal name is what automation binds to. Also review the property's history. If somebody consolidated two similar properties, new data may now land on the surviving property while your workflow still points at the old one.
3. The trigger uses a list that is now empty, or was switched from active to static.
   Open Contacts → Lists and find the list named in the trigger. Check two things. First the member count: if it reads zero, the list criteria are the real problem, not the workflow. Second the list type. An active list keeps adding new members. A static list is frozen. If someone converted an active list to static, everyone already in it was processed and no new contacts will ever arrive.
4. Re-enrollment is off, so contacts who already went through never come back.
   By default a contact enrolls in a workflow once. Open the workflow, go to the enrollment trigger panel, and look at the re-enrollment section. If no triggers are ticked there, a contact who submitted the form last year will not be enrolled when they submit it again. This looks exactly like a broken workflow when your audience is mostly returning contacts.
5. The workflow only enrolls contacts going forward, so historical contacts were never picked up.
   When a workflow is turned on, HubSpot asks whether to enroll existing contacts who already meet the criteria. The default is not to. Check the workflow's settings and its history. If it was switched on without that backfill, and the trigger describes a state most of your contacts already reached, very few people will ever qualify from that point on.
6. A connected integration was disconnected and stopped writing the trigger property.
   Ads tools, third-party forms, calendar and meeting tools, chat and enrichment tools all write properties that workflows commonly trigger on. Go to Settings → Integrations → Connected apps and check whether the relevant app is still connected and still authorised. A revoked token or an expired connection is completely silent from the workflow's side. The property just stops updating.
7. Contacts are suppressed by unsubscribe or bounce status.
   This affects email actions rather than enrollment, but it produces the same feeling that nothing is happening. Open the workflow's performance view and compare how many contacts reached the email action with how many were actually sent. Contacts who unsubscribed, marked a message as spam, or hard bounced are excluded from marketing email sends. Open one affected contact record and check its communication subscription status to confirm.
8. The workflow was cloned, and the clone is the one that is on.
   Search the workflow list for the workflow name. If you see two entries with similar names, or one ending in "(copy)", check which one is active. Editing the original while the clone is the live one is an easy mistake to make, because both look correct when you view them one at a time.
9. A delay step is holding everyone, so completions look like zero.
   Open the workflow and inspect each delay. A long fixed delay, or one that waits for a date property or an event that never fires, will park contacts indefinitely. In the workflow editor you can see how many contacts are currently sitting at each step. If the count is high at a delay and zero after it, enrollment is working fine and the delay is the blocker.
10. API or import volume changed.
    If contacts normally arrive through the API, a CSV import, or a sync from another system, confirm the upstream source is still delivering. Filter Contacts by create date to see whether new records are still arriving at the usual rate, and check the import history for the most recent import. No new contacts means no new enrollments, and the workflow is innocent.
11. An owner-based or team-based branch has unassigned owners.
    If the workflow branches on contact owner, or assigns tasks to an owner, contacts with no owner will fall through or stall. Filter your contacts by "Contact owner is unknown" to see how many are affected. Also check whether a former colleague's user was deactivated, which can leave records pointing at an owner who is no longer there.
12. Someone else turned it off, or edited it.
    Open the workflow and check its history or activity log, which records who changed what and when. This is the fastest way to settle whether the workflow changed or the world around it changed. If the last edit lines up with the date enrollments dropped, you have your answer.

Why HubSpot does not tell you

It helps to look at this from HubSpot's point of view. The workflow is running exactly as configured. The trigger is being evaluated on schedule. Zero contacts match it. Every step that was supposed to happen happened, and in this case that is nothing.

There is no error because no rule was broken. The gap is between what the workflow was configured to do and what you assumed it would do. Software cannot detect that gap on its own, because it holds no record of your assumption. Only a change in the numbers reveals it, and only if somebody is watching the numbers.

What HubSpot does give you

HubSpot has added tooling in this area, and it is worth knowing exactly what it covers.

Workflow Issue Notifications shipped in December 2023. HubSpot’s product team announced them on the Ideas board as live “for all Enterprise customers”, deliverable through Slack, email, Teams, mobile or in-app, configured per workflow. In the settings UI the same area is labelled performance notifications, and HubSpot’s documentation states that “an Enterprise subscription is required to configure performance notifications”. Either way, on Professional they are not an option.

The Workflow Health tab is available on Professional and Enterprise. It lists workflows flagged for review, including ones marked as "Unused", which means the workflow has had zero enrollments for 90 days. That is genuinely useful, with two caveats. You have to open the tab and look at it, because on Professional there is no push notification. And 90 days of zero enrollments is a long wait if the workflow feeds your pipeline.

Between those two, the practical gap is a workflow that broke last week on a Professional portal. Nothing alerts you, and the health tab will not flag it for another three months.

Closing note

That gap is what Workflow Watchdog is for. It checks your active workflows once a day and posts to Slack only when something looks wrong. It looks for four things: zero enrollments in the last 7 days when the prior 7 days had some, enrollments down sharply week over week, validation errors, and workflows with no edits in 90+ days, with the last editor named. Quiet days produce no message.

It is read-only. It never modifies a workflow and it does not read contact records. Free for up to 15 active workflows.

workflow-watchdog-site.onpwr.workers.dev