On this page
What HubSpot does natively
HubSpot logs every action a record goes through. Workflows with errors are listed under Review automation issues on the workflows dashboard, but many problems show only in the action log of the record that hit them, and the workflow keeps going.
Logged as an error, easy to miss:
| What you see | The documented error |
|---|---|
| Email action passed, contact got nothing | “Email was not sent to contact because this is a non-marketing contact.” The workflow continues and skipped emails aren’t resent. Unsubscribed, previously bounced and low-engagement contacts get their own errors |
| Lifecycle stage didn’t change | “The lifecycle stage couldn’t be updated because it would have been set backwards.” Workflows only move it forward unless it’s cleared first |
| Action ran later than expected | “Outside time window settings. Action rescheduled for [new date and time]” |
| AI action left a property blank | The output populated with an empty value, usually because the account ran out of credits |
| Associated record didn’t change | The property couldn’t be set because the record isn’t associated with any target records |
No error at all:
| What you see | What actually happened |
|---|---|
| Email shows as sent, contact didn’t receive it | HubSpot says no error message is expected here |
| Record took the “wrong” path | Branch conditions are evaluated in order; the record follows the first one it meets |
| Value changed, then changed back | Another workflow, form, import or integration wrote the property afterward |
| Record never enrolled | Re-enrollment off, suppression list, or an event trigger that happened before the workflow was on |
How to find why a HubSpot workflow is not working
- Pick one record that should have changed.
- Open the workflow’s enrollment history or action log and find that record. Check whether it enrolled, which branch it took, and the outcome and any error on each action.
- Check the record’s property history. If the workflow set the value and something else changed it later, the Source column shows what.
- Test the workflow with the same record. The Test panel shows which path it would take now and whether it meets the enrollment criteria. Testing doesn’t execute actions.
- Check settings: time windows, pause dates, re-enrollment, suppression lists and goals.
- Look for other writers of the same property. See how HubSpot handles automation conflicts.
Common causes by symptom
- “It worked in testing.” Event-based triggers can’t be tested for enrollment; only the AND filters are checked.
- “It worked last month.” Someone edited it. Check revision history for what changed and who changed it.
- “It works for some records.” Compare a working and a failing record’s properties against each branch condition.
For workflows that do show errors, see how to find and fix HubSpot workflow errors.
Where Jetstack AI fits
When the action log looks clean, the cause is usually in the configuration, and a Jetstack AI Workflow Audit reads it across every workflow at once. It flags potential competing writes to the same property, contradictory branches no record can reach, branches that don’t match the enrollment criteria, re-enrollment with no goal or suppression, circular trigger chains, and references to lists, forms, emails or workflows that no longer exist. It also captures HubSpot’s own validation errors and warnings for each workflow. Every finding points to the exact workflow and action, so you go straight to the right record’s action log to confirm. See how to read the findings.
Sources
- Troubleshoot common workflow errors (HubSpot Knowledge Base)
- Test your workflow (HubSpot Knowledge Base)
- Set event enrollment triggers (HubSpot Knowledge Base)
- Understanding Workflow Audit results (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
See what needs work before you change it.
A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.
Explore Portal Audit