On this page
What HubSpot supports natively
HubSpot has a few built-in protections against loops:
| Protection | What it prevents |
|---|---|
| Go to workflow only enrolls into a workflow of the same type, and skips records already enrolled and active there | A record entering the same target twice at once |
| Go to other action can only be added inside if/then branches | Unbranched loops inside one workflow |
| Create-record actions are skipped if the new record would meet the workflow’s own enrollment criteria | A workflow creating records indefinitely |
| Re-enrollment is off by default | Records going through a workflow more than once |
What HubSpot doesn’t detect is a loop across workflows through properties. Workflow A sets a property; that change enrolls the record in workflow B, which sets another value; that change re-enrolls the record in A. Each workflow is valid on its own, so nothing warns you. The Connections tab shows the assets a single workflow uses, not the chain.
How to find circular HubSpot workflows
- Start from the symptom. Open an affected record’s property history. A value flipping between two states, with workflow sources, points at a property loop.
- List workflow-to-workflow enrollments. For each workflow with a Go to workflow action, note the target. Draw the arrows; any path that returns to its start is an enrollment cycle.
- List property handoffs. For each workflow, note the properties it writes and the properties its triggers and re-enrollment triggers read. An arrow runs from the writer to every workflow that reads the same property.
- Check re-enrollment on every workflow in the cycle. A loop needs at least one workflow that lets records back in.
- Break it at one point. Usually by narrowing an enrollment trigger (add “and value is not X”), turning off re-enrollment for that trigger, or making one workflow the only writer of the property.
Common mistakes
- Two “fix-up” workflows. One sets a value when a field is empty; another clears it when a condition fails. Records bounce forever.
- Re-enrollment on “is known”. Re-enrollment with “is known” fires every time the value changes, so any other workflow that edits the property re-enrolls the record.
- Deleting a workflow to stop a loop. Turn it off instead; deleting loses the configuration you need to diagnose the problem.
Where Jetstack AI fits
A Jetstack AI Workflow Audit builds a dependency graph of every workflow and reports circular dependencies as findings. For any workflow you can see its upstream and downstream enrollment paths, and a path marked as a cycle loops back to the selected workflow. It also flags potential handoffs, where one workflow writes a property another reads, which is where property loops start. Findings describe configuration, so confirm on real records. See dependencies and enrollment paths.
To break a loop by giving the property one writer, build that replacement workflow with Jetstack AI Projects. State the property, the trigger and the condition that stops records re-entering in the brief; you review the plan, approve generation, check the generated workflow and approve deployment separately, then get a receipt read back from HubSpot. The new workflow is created switched off, and Projects doesn’t change the looping workflows themselves, so you turn those off in HubSpot. Projects is currently in limited release; see deploying and receipts.
Sources
- Choose your workflow actions (HubSpot Knowledge Base)
- Workflows FAQ (HubSpot Knowledge Base)
- Add re-enrollment triggers to a workflow (HubSpot Knowledge Base)
- Workflow Audit API: dependencies and enrollment paths (Jetstack AI documentation)
Checked October 29, 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