ColdOps
All posts
Agency operations

Instantly campaign not sending? 9 causes, checked in order

By Mo Charradi, Founder6 min read

An Instantly campaign not sending is almost always one of nine causes — and they're checkable in about five minutes if you go in order of likelihood instead of re-saving the campaign and hoping. Work them most-common first.

The 9 causes, fastest to check first:

  1. The campaign isn't actually active
  2. You're outside the schedule window (wrong timezone)
  3. No leads left to contact
  4. Daily sending limits are exhausted
  5. A mailbox disconnected or errored
  6. An account is in warmup-only mode
  7. Verification is holding leads back
  8. The sequence has no valid next step
  9. An account- or billing-level pause

Most cases are 2, 3, or 5. The detail on each is below.

1. The campaign isn't actually active

Obvious, but it catches everyone: drafts and paused campaigns look nearly identical to active ones at a glance. Check the status toggle. If a teammate paused it "just for a minute" three days ago, this is where you find out.

2. You're outside the schedule window

Campaigns only send inside their schedule — specific hours, specific days, in the schedule's timezone, not yours. A campaign scheduled 9–5 in America/New_York looks dead all morning to an operator in Europe. Check the schedule tab and its timezone before anything else; this is the single most common "it's broken" that isn't.

3. No leads left to contact

If every lead has completed the sequence, replied (stop-on-reply), bounced, or unsubscribed, the campaign shows active and sends nothing — silently. Check the lead counts: if "completed + replied + bounced" roughly equals your list size, the campaign didn't break. It ran out of road — top up the list.

4. Daily limits are exhausted

Sends stop for the day when the campaign or its accounts hit their daily caps — then resume tomorrow. If sending happens early in your window and stops, you're watching limits work as designed. Compare today's sent count against accounts × per-account limit. (And resist solving this by raising limits past the safe range — that trades a slow day for a burned domain.)

5. A mailbox disconnected or errored

Auth expires, passwords rotate, providers suspend — and a disconnected mailbox just stops, taking its share of daily volume with it. One dead account in a five-account campaign is a silent 20% volume cut; all of them dead is "campaign not sending." Check each account's connection status. This is the failure that hides longest because nothing announces it.

6. Warmup-only mode

If an account is set to warmup without campaign sending enabled (or a new account hasn't been added to the campaign's sender list at all), it warms happily and sends zero campaign email. Verify each account is both connected and attached to the campaign.

7. Verification is holding leads back

If lead verification is enabled, unverified or risky leads can be held out of sending. A list that imported "fine" but verified poorly leaves the campaign with far fewer sendable leads than the list count suggests.

8. The sequence has no valid next step

Broken step delays, an empty email body in one variant, or a sequence that ends earlier than you think — worth a 60-second read-through of the sequence tab, especially after edits.

9. Account-level or billing-level pauses

Workspace suspensions, billing lapses, and provider-level sending pauses sit above all campaign settings. Rare, but when nothing else explains it, check the workspace banner and billing state.

The real fix: notice on day one, not day four

Every cause above produces the same symptom — volume quietly below plan — and the dashboard looks "active" the whole time. The difference between a non-event and a lost week is how fast someone notices the sent-count dipped. Working this checklist across every client workspace, one login at a time, is exactly where the noticing slips.

That's a monitoring problem, not an Instantly problem. ColdOps watches sending volume, mailbox status, and campaign activity across every client workspace (Instantly, Smartlead, and EmailBison) and flags "this campaign went quiet" or "this mailbox died" the day it happens — before the weekly numbers come in light. If you run campaigns for clients, a free health snapshot of your setup takes five minutes; connecting a workspace is one read-only API key, and the Instantly integration page shows exactly what data it reads.

Work the list top to bottom and you'll find it — numbers 2, 3, and 5 account for most cases we see.

Frequently asked

Why is my Instantly campaign active but not sending?
The most common causes: the schedule window doesn't match your timezone expectation (sends only happen inside the campaign's schedule, in the schedule's timezone), every lead has already completed the sequence or replied, or the attached mailboxes have hit their daily limits or disconnected. Check status, schedule, lead availability, and mailbox health in that order.
Why are my Instantly emails stuck in queue?
Queued-but-not-sent usually means the daily sending limit is exhausted for the day (campaign-level or account-level), the schedule window has closed, or the sending accounts are paused, disconnected, or in an error state. New campaigns also ramp gradually rather than sending everything at once.
How many emails does Instantly send per day per account?
Whatever the account's daily limit is set to — but the safe practical range for warmed mailboxes is 20–30 cold sends per day each. If your campaign 'stopped sending,' multiply accounts × daily limit and compare to what the campaign already sent today; hitting that ceiling looks identical to a stall.
Why did my Instantly campaign stop sending suddenly?
A campaign that was sending and then stopped is almost always a mailbox that disconnected, a daily sending limit that filled up for the day, the schedule window closing, or an account- or billing-level pause — not a broken campaign. None of these announce themselves, so the sent count just quietly drops. Check mailbox connection status and today's sent-vs-limit first; together they explain most sudden stops.
How do I know if an Instantly mailbox has disconnected?
Every sending account shows a connection status in Instantly, and a disconnected or errored account stops sending its share of volume silently — one dead mailbox in a five-account campaign is a 20% cut nobody sees. Open the accounts view and look for any account that isn't in a healthy connected state, then reconnect it. This is the failure that hides longest, which is why it's worth monitoring rather than spot-checking.

Keep reading