---
title: "HubSpot audit revealed broken workflows: where to start"
description: "Your HubSpot audit revealed hundreds of broken workflows. Where to start: triage by customer impact, turn off what's unused, then fix conflicts in order."
url: "https://jetstack.ai/answers/hubspot-audit-broken-workflows-where-to-start/"
---

# Our HubSpot audit revealed hundreds of broken workflows. Where do we start?

Start with the workflows that touch customers or revenue right now: ones sending email, setting lifecycle stage or rotating owners. Fix critical conflicts there first, turn off workflows with no recent enrollments after checking them, and leave cosmetic issues such as naming for last. When an audit has revealed hundreds of broken workflows, triage by impact, not by count.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

On this page

## What HubSpot supports natively

HubSpot can show you which workflows need attention, but not which to fix first.

| Native view            | What it shows                                                                              | Limit                                            |
| ---------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------ |
| Workflows Health tab   | Workflows set to “Needs review” and unused workflows (no enrollments for at least 90 days) | Professional or Enterprise; no ranking by impact |
| Review workflow issues | A list of issues in one workflow to fix or ignore                                          | One workflow at a time                           |
| Action logs            | Each action’s result, with timestamps, kept for 90 days                                    | Doesn’t show conflicts with other workflows      |
| Enrollment history     | Enrollments up to 6 months old                                                             | Per workflow                                     |

None of these tell you that two workflows are setting lifecycle stage to different values for the same contacts. That’s the kind of finding that matters most and is hardest to see one workflow at a time.

## Where to start with hundreds of broken workflows

1. **Freeze new builds.** Ask the team not to add workflows until triage is done. Otherwise the list keeps growing.
2. **Sort by customer and revenue impact.** First: workflows that send marketing email, set lifecycle stage or lead status, rotate owners or create deals. A broken nurture email reaches customers; a badly named internal alert doesn’t.
3. **Fix live conflicts first.** Two workflows writing different values to the same property, or a contact enrolled in both a customer and a prospect nurture, cause visible damage today.
4. **Turn off what nobody uses.** Check unused workflows with their owner, then turn them off rather than delete them.
5. **Fix errors in what remains.** Missing properties, deleted lists and failed email sends.
6. **Leave naming and folders for last.** They help maintenance, not customers.
7. **Re-audit and compare.** Count conflicts and low scores again so you can show progress.

For a general method that applies beyond workflows, see [how to prioritize audit findings](https://jetstack.ai/answers/prioritize-hubspot-audit-findings). If the list is so long that fixing looks slower than rebuilding, read [fix or rebuild](https://jetstack.ai/answers/fix-or-rebuild-messy-hubspot-portal).

## Common mistakes

- Fixing the noisiest workflow instead of the most harmful one.
- Deleting inactive workflows that are really seasonal.
- Changing a heavily connected workflow without checking what depends on it.

## Where Jetstack AI fits

Jetstack AI’s [Workflow Audit](https://jetstack.ai/audit) scores every workflow from 0 to 100, lists conflicts by severity (critical, high, medium, low) and maps which workflows depend on each other, so you can see the knock-on effect of a change before you make it. It doesn’t change the workflows. When a workflow is beyond repair, or a whole process needs redoing, build the corrected version with [Projects](https://jetstack.ai/build), currently in limited release: describe the logic in a brief, approve the plan, then approve deployment separately. The new workflow is created switched off, so you can test it before you switch it on and turn off the old one; Projects doesn’t edit workflows it didn’t build. See [understanding workflow audit results](https://jetstack.ai/docs/audits/workflow-audits/results) and [deploying with Projects](https://jetstack.ai/docs/projects/deployment).

## Sources

- [Monitor your workflow health (HubSpot Knowledge Base)](https://knowledge.hubspot.com/workflows/monitor-your-workflow-health)
- [Understand your workflow details page (HubSpot Knowledge Base)](https://knowledge.hubspot.com/workflows/understand-your-workflow-details-page)
- [Understanding workflow audit results (Jetstack AI documentation)](https://jetstack.ai/docs/audits/workflow-audits/results)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

Portal audits

## 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](https://jetstack.ai/audit)

On this page

Portal audits

## Related questions.

Our HubSpot audit revealed hundreds of broken workflows. Where do we start?

Start with the workflows that touch customers or revenue right now: ones sending email, setting lifecycle stage or rotating owners. Fix critical conflicts there first, turn off workflows with no recent enrollments after checking them, and leave cosmetic issues such as naming for last. When an audit has revealed hundreds of broken workflows, triage by impact, not by count.

Should we delete unused workflows?

Turn them off first and keep them for a while. HubSpot flags a workflow as unused after 90 days with no enrollments, but some run once a year. Check the purpose with the owner before deleting.

How do we stop this happening again?

Agree a naming convention, a named owner for each workflow, and a rule that new workflows are reviewed before they go live. Then re-run the audit on a schedule and compare.

Is 'broken' the same as 'has errors'?

No. Some workflows show action errors; others run without errors but conflict with another workflow or enroll the wrong records. Treat both as findings, but fix live conflicts first.
