Why are my sequence enrollments ending early?

If you notice that your sequence enrollments are ending unexpectedly after only one or two steps, there could be a few reasons for this. Here are some common causes and how to address them:

Check for Exclusions

Exclusions can cause sequence enrollments to end prematurely. One common exclusion that may affect your sequences is the "Recent Manual Email" exclusion. Exclusions can prevent contacts from enrolling initially or cause enrolled contacts to be unenrolled mid-sequence.

Verify Your Sequence Ruleset: Before investigating specific exclusion criteria, first confirm that your sequence is using a ruleset with exclusions enabled. Navigate to your sequence → Settings → Ruleset to check which ruleset is applied. If the ruleset is set to “default” and exclusions aren't working, the default ruleset may have all exclusions toggled off. You can modify the default ruleset by going to Settings → Sequences → Rulesets tab.

Company-Level vs People-Level Exclusions

Understanding the difference between company-level and people-level exclusions is critical for predicting exclusion behavior:

• Company-level exclusions automatically exclude all people associated with those companies. If you exclude 86 companies, you may see thousands of people excluded because every contact at those companies is blocked from enrollment.

• People-level exclusions only exclude the specific contacts you select, not their entire company.

• If your goal is to exclude only specific contacts at certain companies (not everyone at the company), use a people-level exclusion for that subset. Reserve company-level exclusions only for companies you want fully excluded.

• Higher-than-expected excluded counts often occur when company-level exclusions pull in large numbers of associated contacts, or when duplicate/variant company records aggregate more contacts than anticipated.

Additional Automatic Removal Triggers

• Contacts who click the email opt‑out link are automatically unenrolled from all active sequences

• If the sender's mailbox ownership changes, contacts enrolled using that mailbox will be automatically unenrolled

Critical toggle behavior

• When enabled: Unify will proactively check for exclusion criteria every 15 minutes and remove contacts from sequences if they meet the conditions, even if they're already enrolled.

• When disabled: Exclusions will only prevent new contacts from enrolling in sequences but will NOT remove contacts who are already enrolled and actively receiving emails. This means contacts can continue through a sequence even after meeting exclusion criteria.

• This exclusion typically matches anyone whose last activity date in HubSpot is less than 14 days ago.

• The last activity date may update when Unify sends the first email, inadvertently triggering the exclusion. This can happen even within the same play - an email sent from a sequence can be written back to your CRM, update the activity field, and cause the contact to be excluded from that same sequence minutes later.

• Timing of exclusion checks: Exclusions are evaluated during sequence execution, not just at enrollment. This means a contact can be enrolled successfully but then excluded minutes later if an exclusion condition is met. CRM-based exclusion checks run approximately every 15 minutes, and exclusion setting changes can take up to 30 minutes to fully propagate.

• Opportunity-based exclusions: If you have exclusion rules based on opportunity criteria (such as when an opportunity is created against an account), these can automatically unenroll contacts from active sequences.

• When the "Sequences" toggle is enabled in your exclusion settings, Unify will proactively check for exclusion criteria every 15 minutes and remove contacts from sequences if they meet the conditions.

• Person-level exclusions may not work immediately for newly created contacts due to caching delays in the system. If you're using person-level exclusions (such as competitor exclusions), new contacts might not be excluded at sequence start but could be excluded after the first email is sent, causing enrollments to end early. To prevent this issue, consider using company-level exclusions instead of person-level exclusions, especially for criteria like competitor identification.

Exclusion Hierarchy Details

• Universal exclusions apply by default to all audiences, but can be toggled off at the audience level.

• Audience-level exclusion settings can override universal exclusions by disabling them for specific audiences.

• Sequence-level exclusions always take precedence over both universal and audience-level settings.

• If your universal exclusion isn't working as expected, check if it has been disabled at the audience level.

Advanced Mid-Sequence Monitoring

• Contacts can be unenrolled mid‑sequence when exclusion criteria are met (such as when an opportunity is created after the sequence has started).

• CRM‑based exclusions typically update every 15 minutes, so there may be a brief delay between when an opportunity is created and when the contact is unenrolled.

• This monitoring happens independently of the initial enrollment checks.

Additional Troubleshooting Steps

1. Verify ruleset configuration: Check that your sequence is using a ruleset with exclusions enabled (Sequence → Settings → Ruleset). If exclusions aren't applying, the ruleset may have all exclusions toggled off.

2. Check sequence‑level settings first: Navigate to your sequence settings and review exclusions at the sequence (global) level, as these override play‑level exclusion rules.

3. Audit last activity date exclusions: If the Sequences toggle is enabled, verify any exclusions using “last activity date” criteria to avoid self‑triggering unenrollment.

4. Test configuration changes: Remember that exclusion setting changes can take up to 30 minutes to fully propagate, so allow adequate time when testing new configurations.

Enhanced Troubleshooting Methods

Direct Exclusion Identification

If you receive a notification when trying to add contacts to a sequence (such as from LinkedIn), this indicates the contact matches an exclusion rule. To identify which specific exclusion is affecting the contact:

1. Navigate to Contacts and search for the person by email

2. Click on their contact record

3. Select the "Exclusion" tab to see which exclusion criteria they match

Test Audience Method

To identify the specific exclusion affecting a contact, create a test audience with just that contact's email (email is equal to contact@example.com), then toggle individual exclusions on/off at the bottom of the audience settings to see which exclusion the contact falls into.

How to Resolve

1. Review your exclusion settings, particularly the "Recent Manual Email" exclusion.

2. Consider adjusting the timeframe for this exclusion or creating a more specific exclusion that doesn't interfere with your sequence.

3. Navigate to your sequence settings and review the exclusions applied to ensure they align with your intended sequence behavior.

4. If using opportunity-based exclusions, verify that the "Sequences" toggle is enabled in your exclusion settings to ensure contacts are automatically removed when opportunities are created against their accounts.

5. To prevent activity-based exclusions from triggering due to Unify's own email activity, consider toggling off "Exclude from Sequences" for activity-based exclusions, or adjust your CRM automation that updates the "last activity" field.

6. If using person-level exclusions for new contacts, switch to company-level exclusions when possible to avoid caching delays that can cause exclusions to trigger mid-sequence.

Clarifying the “Sequence attempt was blocked” Error Message

When bulk adding contacts to sequences, you may encounter a “Sequence attempt was blocked — Failed to add all People to Sequence” notification. This is expected behavior when some contacts don’t meet enrollment criteria, not a system error.

You may experience a short delay before you can retry while eligibility checks complete.

To identify why specific contacts were blocked from enrollment, navigate to your sequence’s Enrollments tab and check the Not Enrolled section. This provides per‑contact reasons for enrollment failures and is often the fastest way to diagnose blocking issues.

• Already enrolled in another sequence: Contacts can only be enrolled in one active sequence at a time.

• Recent enrollment cooldown: Re‑enrollment timing rules may prevent contacts from being added to sequences too quickly after previous enrollments.

• Company-level enrollment caps: Your organization may have reached the maximum number of enrollments allowed at the company level.

Sequence vs Play Level Exclusion Precedence

When an exclusion is disabled at the sequence (global) level, contacts can bypass that exclusion even if it is enabled at the play level. Verify that the relevant exclusions are enabled at the sequence level to ensure they take effect across all plays.

Other Potential Causes

While exclusions are a common cause, also consider these factors:

• Manual unenrollment: Ensure that team members aren't accidentally unenrolling contacts.

• Missing variables: Contacts may be blocked from progressing if required variables (e.g., Company Name) are missing.

• New exclusions: Check if any new exclusions were added while the sequence was running.

Understanding Variable Population Differences

Audience‑based enrollments vs CSV uploads: If your audience is built on conditions rather than a CSV upload, custom fields may not be populated even if they exist in your sequence template. This can lead to high block rates when contacts lack the required variable data.

CSV upload mapping: Variables that aren’t mapped during a CSV upload remain empty, causing contacts to be blocked even though the source file contains the data.

Identifying Variable‑Related Block Issues – When you see a large percentage of contacts with “Blocked” status on the sequence details page, check which variables are missing (e.g., Company Name, Company Status, or other custom fields used in the sequence).

1. Upload a CSV with all required fields properly filled and mapped during the upload process.

2. Or switch to an audience that already has the necessary data populated in your CRM.

3. Verify that all sequence template variables have corresponding data in contact records before enrollment.

Critical Global Exclusion Information

Global exclusions operate at two levels that work together:

1. Global exclusion rules (Settings > Organization > Exclusions) – Define which contacts match exclusion criteria

2. "Exclude from Sequences" toggle – Controls whether matching contacts are blocked from sequence enrollment

Even if you disable an exclusion at the ruleset or audience level, contacts will still be blocked if the global exclusion has "Exclude from Sequences" enabled. To allow enrollment of contacts matching a global exclusion, you must toggle off "Exclude from Sequences" in the global exclusion settings (Settings > Organization > Exclusions), not just disable it at the ruleset level.

If contacts are still being excluded after adjusting ruleset or audience exclusions, you need to modify settings in two places:

1. Navigate to Settings > Organization > Exclusions

2. For each relevant exclusion, toggle off "Exclude from Sequences"

3. Also disable the exclusion in your specific Ruleset (Settings > Features > Sequences > Rulesets tab)

4. Wait approximately 30 minutes for changes to propagate before attempting enrollment

5. After successfully enrolling contacts, re-enable the exclusion settings to prevent unintended enrollments in other sequences

Enrollment Method Limitations

Audience‑level exclusions apply to all enrollment methods, including manual enrollment. If you need to bypass exclusions, ensure the exclusion toggles are disabled and allow 30 minutes for processing before attempting enrollment.

Troubleshooting Steps

1. Verify sequence ruleset settings: Navigate to your sequence → Settings → Ruleset to confirm exclusions are enabled in the applied ruleset. If using the default ruleset, check Settings → Sequences → Rulesets tab to ensure exclusions are toggled on.

2. If you notice enrollment drop-off from an uploaded list, use the play-level exclusion toggle method to identify which exclusions are preventing initial enrollment.

3. Look for contacts with "Blocked" status and investigate why they might be blocked.

4. For contacts blocked by exclusions you want to bypass:

   • Check the contact's Exclusions tab to identify which specific exclusions apply

   • Go to Settings > Organization > Exclusions and toggle off "Exclude from Sequences" for those exclusions

   • Also disable the exclusions in your Ruleset (Settings > Features > Sequences > Rulesets tab)

   • Wait 30 minutes for changes to propagate

   • Duplicate and re-run the play

   • Immediately re-enable the exclusion settings after enrollment to prevent affecting other sequences

5. Verify that all necessary contact information and variables are present for enrolled contacts.

6. If the issue persists, contact Unify support for further assistance.

Understanding Queued Status with Exclusions

Contacts may appear as “queued” in a sequence even when they match exclusion criteria. This is expected behavior: exclusions are checked at the moment an email is sent, not when the contact is initially placed in the queue.

• Exclusions are evaluated at send time, not at enrollment.

• Contacts matching exclusion rules are automatically skipped when the sequence runs.

• No action is required from you—the system prevents excluded contacts from receiving emails even though they appear as queued.