Troubleshooting sequence enrollments

When a sequence isn't enrolling contacts the way you expect — they're skipped, blocked, ending early, or showing up as canceled — the diagnostic process is usually the same. Start at the Enrollments tab, find the per-contact reason, then jump to the relevant fix.

Always start here: the Not Enrolled breakdown

1. Open the sequence and click the Enrollments tab (or open the originating Play and click the Sequence node in Metrics).

2. Look at the Not Enrolled count.

3. Click it to see the per-contact reason.

Every failure has a labeled reason. The rest of this article maps each reason to its cause and fix.

The enrollment status labels you'll see

Sequence enrollments move through display statuses in the UI: Draft, In progress, Started, Queued, Blocked, Paused, Finished, Completed, Canceled, Excluded, Bounced, Bounce stopped. A separate Not Enrolled view shows contacts who never started in the sequence.

If you see one of these labels and don't know what it means, the sections below cover the common cases.

"Already Enrolled" / "Recently Enrolled"

The contact is currently in another sequence, or was recently and is within the re-enrollment cooldown.

Default behavior is "never re-enroll." When blockReenrollment is not set on your sequence ruleset, contacts who have been in a sequence cannot be enrolled in another one. There is no automatic time-based cooldown that eventually clears.

To enable re-enrollment:

1. Go to Settings → Organization → Sequences → Rulesets.

2. Enable Allow enrollment into multiple Sequences if you want them in a different sequence simultaneously.

3. Set Minimum days between enrollments to a value (0 for immediate, 30 for monthly, etc.).

4. Wait 30–60 minutes for the change to propagate.

Important: even with re-enrollment enabled, contacts cannot be in two sequences simultaneously — they have to complete or be unenrolled from one before entering another.

Re-enrolled contacts resume at the next step, not step 1.

"Blocked"

A Blocked enrollment means the email couldn't be drafted for that contact. The most common cause is a required template variable that didn't resolve:

• A custom field referenced in the email isn't populated for that contact.

• A snippet's data source isn't returning a value.

• A variable's fallback text isn't configured.

To fix:

1. Open the sequence's Enrollments tab.

2. Filter by Blocked.

3. Open one of the blocked enrollments to identify which variable is missing.

4. Either populate the missing data on the contact (in the contact's record or CRM) or update the sequence copy to handle missing values gracefully.

After fixing the data, blocked enrollments progress on the next evaluation cycle.

"Canceled"

A canceled enrollment was removed from the sequence before completion. Common causes:

• Manual unenroll — someone unenrolled the contact (deliberately).

• Proactive unenrollment from an exclusion — the contact matched an exclusion rule that has proactive unenrollment enabled, so they were removed mid-sequence.

• Sequence was deleted or canceled at the sequence level.

To verify which: click the canceled enrollment and check the activity history. If it was proactive unenrollment, you'll see the exclusion rule that fired.

Important gotcha: activity-based exclusions can self-trigger. Unify's email writeback updates CRM activity fields, which can then match an "activity within X days" exclusion. For activity-based exclusions, keep proactive unenrollment off.

"Excluded"

The contact matched an exclusion rule. The rule could be at any of three levels:

• Organization-level exclusion (Settings → Organization → Exclusions).

• Sequence ruleset exclusion (per-sequence overrides on top of the org defaults).

• Audience-level exclusion (filters on the Play's audience).

The organization level takes precedence. Disabling at the ruleset alone won't bypass an exclusion if the org-level Exclude from Sequences toggle is on.

To diagnose which rule blocked a specific contact:

1. Open the contact's record → Exclusions tab.

2. You'll see every rule the contact matches.

To temporarily bypass an exclusion:

1. Disable at the org level (Settings → Organization → Exclusions).

2. Disable at the ruleset level for the sequence.

3. Wait 30–45 minutes for propagation.

4. Re-run the Play.

See How can I determine which rule caused an exclusion? for the deep dive.

"No routing target"

The contact's persona has no matching route configured in the Sequence Enrollment node of the originating Play.

Fix:

• Open the Play and edit the Sequence Enrollment node.

• Add a route for that persona.

• Or add an "Everyone else" catch-all route so unconfigured personas land somewhere.

For persona-specific Plays (New Hire, Champion Tracking), the persona must also be enabled in the relevant Settings panel.

Delay between matching audience and enrollment

Audience matches are evaluated on a ~15-minute polling cycle. If you just updated your audience criteria or added new records, allow 15–30 minutes before assuming the enrollment isn't going to happen.

If the delay persists beyond an hour, check:

• CRM sync hasn't caught up — Salesforce and HubSpot sync every 15 minutes by default. A contact added to the CRM recently may not be in Unify yet.

• The audience itself isn't matching — preview the audience builder and confirm the contact appears.

• A sequence-level exclusion is filtering — see "Excluded" above.

Sequences ending early

If a sequence is completing for contacts before reaching the final step:

• A reply was received. Replies that aren't classified as Out-of-Office set the enrollment's isReplied flag, which can cause the sequence to stop sending further steps to that contact.

• Out-of-Office reply was received. OOO replies trigger a separate OOO event flow rather than marking the enrollment as replied. OOO contacts typically remain in the sequence and receive subsequent steps once the OOO period ends.

• The contact bounced. Once a recipient bounces, sequencing stops for that contact (status: Bounced or Bounce stopped).

• The contact unsubscribed. Sequencing stops on unsubscribe.

• Manual completion — someone marked the enrollment complete.

• Proactive unenrollment from an exclusion — covered under "Canceled" above.

When the same contact keeps failing

If a specific contact keeps showing up as Not Enrolled across multiple attempts:

1. Open the contact's record.

2. Check the Exclusions tab — what rules do they match?

3. Check Activity — what sequences are they currently or recently in?

4. Check that they have a valid email and verified domain.

For account-specific debugging beyond this, escalate to support with the contact ID, sequence link, and the specific Not Enrolled reason.