HubSpot Workflow Re-enrollment: Why Contacts Don't Come Back (or Come Back Too Often)

A HubSpot workflow enrolls each record once, the first time it meets the trigger. If you want a returning lead to go through again, you have to turn re-enrollment on and pick which triggers count. If the opposite is happening and people keep getting the same emails, re-enrollment is on and one of those triggers fires more often than you think. Both problems live in the same place: the workflow's enrollment trigger settings. Its enrollment history shows you which one it is.

Workflows need a Professional or Enterprise subscription, according to HubSpot's help pages. On Free or Starter, this doesn't apply yet.

The default is once and done

HubSpot's own wording is that records "are only enrolled in workflows the first time they meet the workflow enrollment triggers or are enrolled manually."

Here's how that bites. Someone fills out your contact form, goes through your follow-up workflow, and finishes it. Months later they come back and fill out the same form again. If re-enrollment is off, the workflow does nothing the second time, and it's easy to miss. The new submission sits on the contact record and nobody gets a task.

Symptom one: returning leads get nothing

Open the workflow and check whether re-enrollment is on at all.

1. Go to Automation, then Workflows, and click the workflow's name.
2. Click the enrollment trigger box at the top.
3. For a contact-based workflow, open the Re-enrollment tab and look at the Allow contacts to re-enroll after completing the workflow switch. For company, deal and other workflow types, it's on the Settings tab, under the Re-enroll switch.
4. If it's on, look at which triggers have a checkbox ticked. Only the ticked ones count.

If re-enrollment is on and people still don't come back, check these:

• The record never left. A record won't re-enroll while it's still in the workflow. If your workflow has long delays, someone who's halfway through can't start again until they exit or you unenroll them.
• The trigger can't be used for re-enrollment. Activities and activity properties can't be. HubSpot lists the ones that won't work under "The following enrollment conditions can't be used for re-enrollment" on that same tab, so check there before you assume anything.
• A multi-value operator. In contact-based workflows, a single trigger like "is any of" with several values can't be used for re-enrollment. HubSpot's fix is to split it into separate triggers, one value each.
• They don't meet the original criteria anymore. A record has to meet the initial enrollment criteria and at least one re-enrollment trigger. If the original trigger also says "Lifecycle stage is Lead" and they've since become a Customer, they won't re-enroll.
• They never enrolled the first time. Turning re-enrollment on isn't retroactive. Records that never enrolled have to be enrolled manually.

One more trap: date and number refinements don't apply to re-enrollment. If your trigger says "filled out this form between two dates," the date range is ignored for re-enrollment, and anyone who submits the form again re-enrolls.

Symptom two: the same people go through again and again

This is the one that gets complaints. When a record re-enrolls, it starts from the beginning and completes every action again, including automated emails.

The first thing we check is any trigger that says "is known." Look for these:

• "Is known" triggers. If you use "is known" on a property, the record re-enrolls when the property gets a value and every time it changes from one value to another, as long as it still meets the workflow's original triggers. HubSpot's example is "Lifecycle stage is known": each time the stage updates, the contact re-enrolls. If another workflow or an integration keeps changing that property, every change is a fresh start. Lifecycle stage has its own rules too, covered in why lifecycle stages only move forward.
• List membership. A contact re-enrolls each time they join the list again. If the list's criteria depend on a field that something keeps clearing and refilling, people drop out and rejoin, and each rejoin is a new enrollment.
• Event triggers set to fire every time. Event-based workflows have their own question: "Should [object] be re-enrolled in this workflow?" If it's set to Yes, re-enroll every time the trigger occurs, every form submission or event starts the workflow over.

The fix is to pick the narrowest trigger that means what you want. "Lifecycle stage is any of Sales Qualified Lead," with that one value, re-enrolls on one specific change. "Lifecycle stage is known" re-enrolls on any change.

Then add a way out. On the same Settings tab you can set unenrollment conditions, and in contact-based workflows you can remove contacts who no longer meet the criteria, meet the workflow goal, or have been added to a suppression segment. A suppression segment of current customers is a simple guard on a sales nurture.

Turning it on in a live workflow is the risky step

When you save re-enrollment changes on a workflow that's already on, HubSpot asks whether you want to enroll existing contacts (or existing companies, deals and so on).

Read that dialog slowly. HubSpot's own advice is that if the workflow has been on for a while, you may want Save and don't enroll existing contacts to avoid re-enrollments. If you pick the other option on a workflow that sends email, you can send the whole sequence again to everyone who already qualifies.

How do I see who re-enrolled? Check enrollment history

Don't guess. HubSpot keeps a record of who enrolled and what happened to them.

1. Open the workflow.
2. In the top right of the editor, click Performance history, then Enrollments history. Or from the menu in the top left, click View, then Enrollment history.
3. Search for a record that you think should have enrolled, or one that got an email twice.
4. Hover over its name and click View logs. You'll see the path it took, and actions with errors show in red.

The workflow's details page has an Action logs tab too. You can filter by event type, including errors, and export the log to a CSV. HubSpot says enrollment history is kept for 6 months and full action log data for 90 days, so check soon after you notice a problem.

Merged contacts are their own case

By default, HubSpot doesn't enroll merged contacts in a workflow, even if the merged record meets the criteria. Contact-based workflows have a setting, Automatically enroll merged records if the updated merged record meets the enrollment conditions. If you're cleaning up duplicate contacts and people seem to fall out of your automation, check it.

A short checklist

For every active workflow that sends email or creates tasks, write one line each. If you've just taken over the portal, our post on where to start with a messy HubSpot portal puts this alongside the other first checks.

1. Is re-enrollment on? Which triggers are ticked?
2. Does any trigger use "is known" on a field that something else writes to?
3. Is there an unenrollment rule, a goal or a suppression segment?
4. How long can a record sit inside it before it can re-enroll?

FAQ

Will turning on re-enrollment send emails to people who already finished?

Only if they meet a re-enrollment trigger again, or if you choose to enroll existing records when you save. Choose Save and don't enroll existing contacts if you're not sure.

Can I re-enroll someone by hand?

Yes. Manually re-enrolled records don't have to meet the triggers. Re-enrollment still has to be turned on, though.

Does re-enrollment work on HubSpot Starter?

No. Workflows, and re-enrollment with them, need a Professional or Enterprise subscription, according to HubSpot's re-enrollment page.

Does re-enrollment restart the workflow from the beginning?

Yes. A re-enrolled record starts over and completes every action again, including automated emails.

Why does "is known" re-enroll people constantly?

Because every change to that property's value counts, as long as the record still meets the original triggers. If something keeps rewriting the field, each change starts the workflow again. A single-value "is any of" trigger re-enrolls on one specific change instead.

Re-enrollment is one setting in one workflow. Our Revenue Stack Audit looks at your workflows, forms and integrations together and tells you what to fix first. It's read-only. Want a second set of eyes on your setup? See how the audit works.

Sources (HubSpot Knowledge Base): Add re-enrollment triggers to a workflow, Set event enrollment triggers, Manage workflow enrollment settings, Review your workflow's enrollment history, Review a record's workflow paths and actions, Understand your workflow details page, Create workflows, Merge records.

Independent. Not affiliated with HubSpot. HubSpot is a trademark of HubSpot, Inc.