Real-time alert when an enabled workflow has not enrolled a single contact in over a day. Usually means the trigger criteria broke or a referenced property was renamed.
At a glance
Workflow Stopped Enrolling (>24h) is a real-time silence alert. It watches enabled workflows and fires when one that should be enrolling contacts has not enrolled anyone in more than 24 hours. A workflow can show no errors and still be quietly broken: if its trigger criteria reference a property that was renamed, a list that was deleted, or a value that no contact ever satisfies any more, the workflow stays “enabled” but stops doing anything. Because there is no error event, nothing else flags it. This card is the canary that catches automation that has gone silent before a campaign launches on top of a dead pipeline.
| What it counts | The count of enabled workflows whose most-recent enrolment timestamp is more than 24 hours old. Each alert row carries the workflow name, its last-enrolment time, its trigger type, and the gap in hours since the last enrolment. |
| Enabled-only | Only workflows currently turned on are evaluated. A paused or draft workflow not enrolling is expected behaviour, not an alert. |
| Expected-cadence awareness | The alert is designed for workflows that should enrol continuously (form-submit, list-membership, property-change triggers). Low-frequency workflows that legitimately enrol rarely can be excluded or given a longer silence threshold in the profile, so they do not flag during normal quiet periods. |
| Silence vs error | This is distinct from a workflow throwing errors. A workflow can be erroring loudly (see Workflows With Errors) or failing silently with zero enrolments (this card). The two failure modes need separate detectors. |
| HubSpot Hub scope | All Hubs that support workflows (Marketing Hub, Sales Hub, Service Hub at Professional and above). Starter tiers without workflows show nothing. |
| Currency | n/a (count). |
| Time window | RT (real time). Re-evaluated as enrolment activity arrives. |
| Alert trigger | Any enabled workflow whose last enrolment was more than 24 hours ago. |
| Roles | owner, marketing, engineering. Marketing owns the workflow logic; engineering owns any property sync or rename that may have broken the trigger; the owner needs to know because silent automation means missed nurture and missed revenue. |
Calculation
Calculated automatically from your HubSpot data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A subscription skincare brand on Marketing Hub Professional runs several always-on workflows. Reading on 9 May 26. Last week an engineer renamed a custom contact property fromsignup_source to acquisition_source during a data-model tidy-up. Three of the brand’s workflows triggered off signup_source. They did not error, they simply stopped matching anyone. The card fires:
| Workflow | Trigger type | Last enrolment | Hours silent | Flagged? |
|---|---|---|---|---|
| New-subscriber welcome | List membership | 41h ago | 41 | Yes |
| Sample-to-full-size nurture | Property: signup_source = sample | 46h ago | 46 | Yes |
| Quiz-completed onboarding | Property: signup_source = quiz | 44h ago | 44 | Yes |
| Cart-abandon recovery | Event: checkout started | 12 min ago | 0.2 | No |
| Win-back dormant 90d | Property: last_order_date | 19h ago | 19 | No |
- Three workflows went silent together, which points to a single root cause. When multiple workflows stop enrolling at roughly the same time, look for one shared dependency rather than three separate failures. Here it is the renamed property.
- The welcome workflow is the most expensive silence. It sits at the very top of the funnel; 41 hours of no welcome means every new subscriber in that window got no onboarding email. Those are first-impression moments that cannot be recovered.
- The cart-abandon workflow is healthy, which is the tell. Event-triggered workflows that fire off store activity kept enrolling normally, confirming the break is specific to the property-triggered workflows, not the whole automation engine.
- The win-back workflow is silent but not flagged, and that is correct. It triggers off
last_order_datecrossing a 90-day threshold, which only a handful of contacts hit on any given day. Nineteen hours of quiet is within its normal cadence, so the longer threshold configured for it keeps it from false-alarming. - The fix is a one-line trigger edit per workflow. Point the three broken triggers at
acquisition_source, re-enable, and confirm enrolments resume within minutes. The card clears once each workflow enrols again.
Sibling cards merchants should reference together
This alert is the silent-failure detector for automation. Pair it with these to cover the other failure modes and the volume baseline:| Card | Why pair it with Workflow Stopped Enrolling (>24h) |
|---|---|
| Workflows With Errors | The loud-failure companion. This card catches silent zero-enrolment; that one catches workflows throwing action errors. A workflow can hit either failure mode. |
| Workflows Blocked / Stale | The KPI-count sibling of this alert. This is the real-time trigger; that is the standing count merchants watch on the dashboard. |
| Workflow Error Spike | The rate-of-change alert on errors. Use it alongside this one to tell a broken-trigger silence apart from an error storm. |
| Workflow Enrollments (30d) | The volume baseline. It shows expected enrolment levels so you know which workflows should never go quiet. |
| Active Workflows | The denominator. Knowing how many workflows are enabled frames how many of them have stalled. |
| Top Workflows by Enrolments | Severity context. A silent workflow that is normally a top enroller is a far bigger problem than a silent low-volume one. |
Reconciling against HubSpot
Where to look in HubSpot: HubSpot shows per-workflow enrolment history but does not alert when a healthy-looking workflow quietly stops enrolling. The closest native views:HubSpot → Automation → Workflows and open the workflow, then the Enrollment history tab to see the last contact enrolled and when. HubSpot → Automation → Workflows → (workflow) → Performance for enrolment counts over time. HubSpot → Settings → Properties to confirm whether a property the workflow references was renamed or archived.The merchant traditionally finds a silent workflow only when someone notices the downstream emails stopped, which can be days later. This card surfaces the silence within a day. Why a flag may be expected rather than a real break:
| Reason | Direction | Why |
|---|---|---|
| Naturally low-frequency workflow | Expected flag | A workflow that only enrols on a rare event (annual-renewal, 90-day-dormant) legitimately goes quiet for long stretches. Give it a longer silence threshold so it does not false-alarm. |
| Seasonal or campaign-tied workflow | Expected flag | A workflow tied to a promotion that has ended will stop enrolling by design. Pause it or exclude it rather than leave it enabled and silent. |
| Time zone | Boundary effect | The 24-hour clock is anchored to the portal’s reporting time zone; a workflow that last enrolled just over the boundary can flag or clear depending on the read time. |
| Renamed or archived property | Real break | A trigger pointing at a property that was renamed or archived matches nobody and produces no error. This is the primary case the card catches. |
| Deleted trigger list | Real break | A list-membership trigger whose source list was deleted silently stops enrolling. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| Klaviyo Flows | If the merchant runs both platforms, a property rename in a shared data source can break triggers on both sides at once. | The two platforms reference properties independently, so a HubSpot trigger can break while the Klaviyo equivalent keeps working, or the reverse. |
| Form Submissions (30D) | A form-triggered workflow going silent while form submissions continue is a strong broken-trigger signal. | If submissions also dropped to zero, the problem is upstream (the form itself), not the workflow trigger. |
Known limitations / merchant FAQs
The workflow shows no errors in HubSpot. Why is it flagged? That is exactly the case this card exists for. A workflow with a broken trigger (renamed property, deleted list, an impossible criterion) does not throw an error. It simply matches nobody and enrols nobody. HubSpot’s error reporting stays clean while the workflow does nothing. Silence, not errors, is the signal here. One of our workflows only enrols a few people a month. Will it flag every day? It would, unless you tell the card it is a low-frequency workflow. Give such workflows a longer silence threshold in the profile, or exclude them, so the alert is reserved for workflows that genuinely should be enrolling continuously. We disabled a workflow on purpose. Will it flag? No. Only enabled workflows are evaluated. A paused or draft workflow not enrolling is expected and is ignored. How fast does the flag clear after we fix the trigger? As soon as the workflow enrols at least one contact again, its last-enrolment timestamp updates and the card clears on the next evaluation, usually within minutes once contacts start matching the corrected criteria. Multiple workflows flagged at once. Is that a bigger problem? Often it is one problem, not many. Simultaneous silence across several workflows usually points to a shared dependency that broke: a renamed property, an archived field, a deleted list, or a sync that stopped writing the value the triggers depend on. Look for the common thread before treating them as separate incidents. Does this measure enrolment or email sending? Enrolment. A workflow can be enrolling contacts but failing to send (that shows up as errors or in deliverability cards). This card is upstream of that: it confirms contacts are entering the workflow at all. No enrolment means nothing downstream can happen. Action playbook when this fires:- Open each flagged workflow and read its enrolment trigger.
- Check whether any property, list, or value the trigger references was recently renamed, archived, or deleted.
- If several workflows flagged together, find the shared dependency first; one fix may clear all of them.
- Repair the trigger, re-confirm it matches live contacts, and watch enrolments resume.
- For workflows that legitimately enrol rarely, set a longer silence threshold so they stop false-alarming.