Sequence Sending Health Alerts

Last updated: August 24, 2026

A sequence can go quiet for many reasons, and until now the reason only existed in
our application logs.

Whenever sending is blocked or degraded and the customer has to do
something, that's shown as an alert attached to the sequence.

It is an observability layer only. It never changes sending behaviour, never
pauses a sequence, never adds senders, and never edits a schedule. It reports.

Where the customer sees it

Surface	What appears
Sequence page — header	A red "Action required" button next to the sequence name. Clicking it opens a small dialog with the problem, a plain-English explanation, and a button to the screen that fixes it.
Settings → Alerts	The alert as a record, with its title and "what to do" guidance. Open alerts are listed first; resolved ones sit in a collapsed section.
Email / Slack	Only for the three alter types. Email goes to the organization's configured alert recipients; Slack only if the organization connected Slack and enabled it for alerts.
Sequence list	Nothing. Deliberately — see the FAQ.

The customer always gets the same two levels: a short notification for context, then
the dedicated screen that holds the real detail. The alert never tries to diagnose
things itself.

The seven alerts

One alert per sequence at a time. If a sequence has two problems, the customer sees
the one higher in this table first — the list is in priority order, and faults that
stop sending outright outrank the rest.

Alert	Customer-facing title	What it means	How the customer fixes it	Fix button goes to
`SENDER_DISCONNECTED`	Sender disconnected	The senders this sequence relies on exist but are disconnected or invalid (expired OAuth token, revoked access, password change).	Reconnect the account.	Senders → Accounts
`NO_SENDER_FOR_CHANNEL`	No sender	The sequence has steps on a channel (email or LinkedIn) with no valid, connected sender assigned to it.	Assign a sender for that channel on this sequence — connecting one first if the organization has none.	Sequence → Settings → Sending
`NO_SENDING_WINDOW`	No sending window	The sequence's schedule and its contacts' timezones never overlap, so no send window ever opens.	Widen the sending hours or active days, or align the schedule timezone with the audience.	Sequence → Settings → Sending
`STUCK_PINNED_LEADS`	Stuck leads	Leads are pinned to a specific identity that no longer has a valid sender for the channel it needs, so those leads can never be served.	Reconnect that account, or replace it.	Senders → Accounts
`NOT_PROGRESSING`	Stalled	Leads have been ready to contact for over a week and not one of them has been started. Usually sender capacity is entirely consumed by other sequences.	Check capacity; add senders or lower targets elsewhere.	Senders → Capacity
`LEADS_AWAITING_APPROVAL`	Leads awaiting approval	Every lead is sitting in the approval queue, so nothing is queued to start.	Review and approve the pending leads.	Tasks, filtered to this sequence
`NO_LEADS_ENROLLED`	No leads enrolled	The sequence is active but has no leads at all, so it has nothing to send.	Enroll leads, or link a list.	Sequence → Leads

The three faults that only this feature catches

STUCK_PINNED_LEADS, NO_SENDING_WINDOW and NOT_PROGRESSING appear spontaneously after a setup that used to work, with no event we can hook into. Before this feature nothing detected them at all. The other four either already had their own notification (sender disconnects, approval digest) or are visible the moment the customer looks at their sequence.

Statuses that are never alerted

These are healthy resting states. The customer sees nothing — no banner, no button, no email. Support may still see them when inspecting a sequence.

Status	Meaning
`SENDING`	Leads are queued to start and the sequence is sending.
`ALL_LEADS_FINISHED`	Every enrolled lead reached the end of the sequence. Nothing is broken; enroll more leads to keep sending.
`ALL_LEADS_CONTACTED`	Leads remain, but every one has had its first touch. Follow-ups still fire; nothing new is being started.
`LEADS_ON_HOLD`	Leads are waiting but none are eligible right now — exclusions, pending email verification, or step delays.

Distinguishing these from real faults is the point of the feature: a sequence that
simply finished its leads must never look broken.

Which alerts notify, and which stay silent

All seven are visible in the app. Only three also send an email (and Slack, if
configured):

Notifies the customer	Silent — visible in-app only
`STUCK_PINNED_LEADS`	`SENDER_DISCONNECTED` — the sender-level disconnect alert already emails
`NO_SENDING_WINDOW`	`NO_SENDER_FOR_CHANNEL` — would double up with the coverage-broken alert
`NOT_PROGRESSING`	`LEADS_AWAITING_APPROVAL` — the hourly approval digest already emails
	`NO_LEADS_ENROLLED` — true of any half-finished setup, so never worth an email

The silent ones stay silent on purpose: they either duplicate a notification the
customer already gets, or they would email someone about a screen they are looking at.