Sequence or campaign emails not sending: a checklist

Almost every "my emails aren't sending" report turns out to be Current working exactly as designed — a brake it applied on purpose, in a place nobody looked. Start by answering one question, because sequences and campaigns fail for completely different reasons.

For the full picture of why there are two paths at all, see "How Current sends email — and why two mail paths, not one".

1. 1
   1. Is the sequence switched on?

   Go to Sales → Sequences. Each row has an Active/Paused switch. A paused sequence stalls its enrollments quietly — the worker re-checks them about an hour later and does nothing until you turn the sequence back on. A sequence you create by hand starts Active — the switch only matters if someone turned it off. Only an AI-drafted sequence is saved paused on purpose (its Save button reads "Save as paused sequence", and Current tells you "it stays paused until you turn it on"), so a fresh AI draft sends nothing until you flip it on.
2. 2
   2. Look for the queue-depth line at the top of the page

   If you see "N emails are waiting for tomorrow's window — the daily send limit protects your deliverability", the daily send cap is the answer. Current sends at most 250 sequence emails per mailbox per calendar day (Eastern Time). Email 251 is not an error: it quietly reschedules to the next business morning at 9:00 AM ET. The cap is fixed in code — nobody can raise it from the app.
3. 3
   3. Check the calendar

   Sequences have a "Skip weekends & holidays" switch in the builder, on by default. With it on, an email or task step due on a Saturday, Sunday, or a holiday on your company calendar does not run — it re-arms for the next business morning at 9:00 AM ET. Delay and condition steps are timers and never roll.
4. 4
   4. Open the sequence Report

   Click Report on the sequence row (available to sales leadership, and to the person who created the sequence). The hero band tells you almost everything: Emails sent, Deferred by cap, Unsubscribed, and — under Active now — how many enrollments are paused and need attention. The Exit reasons chart shows why enrollments ended.
5. 5
   5. Read the exits — most "missing" sends are wins

   A sequence auto-exits a contact the moment they reply (you also get a bell notification), if their address lands on the suppression list, or if the linked deal is marked Won or Lost. They stop receiving steps by design, and show in the Recipients table as Replied, Unsubscribed, Deal won, or Deal lost.
6. 6
   6. Chase the paused enrollments

   Filter the Recipients table to Paused. Current pauses one enrollment — never the whole sweep — when it hits something a human must fix.

1. 1
   1. Read the campaign's status chip

   Draft, Pending approval, Approved, Sending, Sent, Failed, or Canceled. A campaign sitting in Draft or Pending approval has not been queued — nothing will go out until it is approved and sent.
2. 2
   2. Did the send get refused at the confirm step?

   Current refuses to queue and tells you why. "Send yourself a test email first" means the test-before-send gate is unmet — every campaign must be test-sent before it can be queued. "This campaign's audience is empty right now" means the filters resolve to nobody. And if NeverBounce is connected and at least half the addresses are unverified or verified over six months ago, you're asked to verify first or confirm anyway.
3. 3
   3. Check who can approve it

   In Current the Approve button only appears for sales leadership, so in practice a marketing campaign needs a leader's approval before it can be queued. A service notice you own goes out on your own approval only up to 25 recipients; above that, Current tells you the count and asks you to get leadership approval first. See "Campaigns and audiences: build, approve, and send safely".
4. 4
   4. Check whether real sending is armed

   Until your workspace has both a sending domain saved and the "Real sending" switch turned on (Integrations → the email card, tenant admins only), the workspace is in preflight mode. In preflight the campaign only goes to your own team, meaning the email addresses on your workspace's active member profiles. Nobody else in the audience is queued, so the report shows one recipient instead of hundreds. If your own profile has no working email address, Current refuses the send outright and tells you to finish email setup. (Any rows queued before preflight was re-armed are marked Failed with a "preflight mode" error by the dispatcher.)
5. 5
   5. Check the clock

   A campaign queued inside the weekend quiet window (Friday 5:00 PM to Monday 8:00 AM, Eastern) is held until the next weekday at 8:00 AM unless the sender ticked "Send now instead" in the confirm dialog. It will look queued and idle all weekend — that is the hold, not a fault.
6. 6
   6. Open the campaign report and read the recipient states

   Suppressed means the contact unsubscribed or was already on the suppression list — Current re-checks that at the moment of send, so a late unsubscribe is honored even after queueing. Failed carries the reason. Bounced and complained addresses are suppressed from future sends automatically.
7. 7
   7. Give a big send time

   The dispatcher paces deliberately: up to 25 recipients per workspace per run, and 100 overall per run, every 5 minutes — so one large blast can't starve another workspace's small notice. A campaign flips to Sent only once nothing is left queued.

• ＋Confirm the sequence has steps at all — a row that says "No steps yet — edit to add some" has nothing to send.
• ＋Confirm someone is actually enrolled. The report's empty state says so plainly: "No one has been enrolled in this sequence yet."
• ＋For auto-enroll rules, the emails send from the mailbox of the person who created the rule — if that mailbox is disconnected, every enrollment the rule creates will pause.