Sistava

Instantly Campaign Not Sending Emails: How to Fix It

How-to — — by Mahmoud Zalt

Launched an Instantly campaign and nothing went out? The documented causes, from schedule windows and daily limits to disconnected sending accounts.

You loaded the leads, wrote the sequence, clicked launch, and the counter stayed on zero. Nothing bounced, nothing errored, nothing sent. It is a horrible place to be, because the tool is not telling you no, it is just saying nothing.

The reassuring part is that a stalled campaign almost never means something is broken. Nearly every cause is a setting behaving exactly as configured, usually a limit or a window you set weeks ago and forgot.

Instantly also ships a shortcut for this. Its documentation points you at the Diagnose button in the campaign's Analytics section, which runs automatic checks before you start reading settings by hand. Start there, then use the sections below to interpret what it tells you.

Has it actually been long enough?

Instantly documents a delay of 10 to 15 minutes between launching a campaign and sending beginning, and the same 10 to 15 minutes after you resume a paused one. It also states that changes to sending accounts can take 10 to 15 minutes to take effect. So the first answer is often patience.

There is a documented way to confirm rather than guess. After waiting fifteen minutes, open the campaign's Analytics and look at the Activity section, filtering by the Email sent event. If sends are happening, the problem is not what you think it is.

Also check the obvious one. A campaign in Draft status has never been launched, and a paused campaign stays paused until you resume it.

Are you inside the sending window?

Instantly's first documented cause is that the campaign is set to send only during specific hours and days, and right now is outside that window. The fix lives in the campaign's Schedule tab. Adjust the window to include the current time, confirm the days you expect are selected, and check the timezone.

One more thing on that tab is easy to miss. Instantly asks you to verify that the campaign's end date has not already passed. A campaign that ran out of runway looks identical to a campaign that never started.

Which limit have you already hit?

There are two separate ceilings and they are easy to confuse. One belongs to the campaign, the other belongs to each sending account, and either one being reached stops sending for the day.

Do the arithmetic before you go looking for a bug. Four accounts at the documented 30 a day is 120 emails, and a list of 2,000 people takes over two weeks at that pace. That is not the tool failing, that is what careful sending looks like.

Why does Instantly say my email account is disconnected?

A campaign with no usable sending account cannot send anything, and Instantly's campaign error guide names this directly. Its documented causes for a disconnected or errored account are DNS records missing or wrong, a problem with the access token from your email provider, the provider's own daily sending limit being exceeded, SMTP being switched off on a Microsoft or Outlook account, and purchased accounts whose subscription was cancelled.

The statuses matter, because one of them needs nothing from you. Instantly documents a Reconnecting badge that means the system detected a connection issue and is trying to fix it, and says no action is required. A Sending Error or Disconnected badge is the one that needs you.

Getting sending accounts back to work

  1. Filter for the broken ones — On the Email Accounts dashboard, filter by Has Errors or Paused so you are looking at the accounts that matter rather than the whole list.
  2. Unpause what is simply paused — Select the paused accounts, click the three-dot menu, and choose Unpause selected accounts. Then resume the campaign and allow 10 to 15 minutes.
  3. Test the domain setup — Instantly documents a Test domain setup action that checks your MX, SPF, DKIM and DMARC records. Missing or wrong records are one of its named causes of bounces and disconnections.
  4. Reconnect the account — Click the three dots next to the email account, choose Reconnect email account, then Connect existing accounts. This is the documented route when the access problem is a token rather than DNS.
  5. For Microsoft and Outlook, mind the wait — Instantly's documented sequence is to enable SMTP for the Outlook account, remove the account from Instantly, wait one hour, then reconnect. It flags that hour as critical, so skipping it tends to reproduce the same error.
  6. Give it a day before escalating — If an account is active but still shows as disconnected, Instantly asks you to wait 24 hours before contacting support, since automatic reconnection handles many cases on its own.

Worth knowing that reconnecting is a per-account job. On Instantly's public feedback board there is an open request titled Reconnect accounts in bulk, with a modest number of votes and several comments. That is a user request rather than a shipped feature, and it tells you something real about how often people are doing this by hand.

The last documented cause is the strangest one to look at, because everything appears healthy and still nothing goes out. Instantly calls it waiting for a lead to process, and it covers every case where the system has leads but has decided not to send to them yet.

Notice how much of this is you managing infrastructure rather than talking to buyers. Schedules, ramps, ceilings, reconnections. It is real work, and it is not the work that wins deals. At Sistava an AI Employee takes the brief and owns the loop, so the sending mechanics stop being a daily chore you have to remember to check.

When Instantly stops you on purpose

One cause deserves its own heading because it is not a fault at all. Instantly documents an automatic pause triggered by a high bounce rate, describing it as recent emails bouncing at a rate typically above 5 percent. The campaign stops to protect your sending reputation.

The documented fix is not to restart it and hope. Verify the lead list with email verification, review your copy with a spam checker, look at the bounce reasons in Analytics, clean the list, and only then resume. If you resume without cleaning, you will trigger the same pause and do more damage on the way.

If bounces are high on a list you bought, that is your answer. A cheap list full of dead or guessed addresses will bounce, and no setting inside a sending tool repairs it. Cut the list back to addresses you have verified and accept the smaller number.

FAQ

How long does Instantly take to start sending after launch?

Instantly documents that it can take 10 to 15 minutes before sending begins once a campaign is launched, provided the current time is inside the sending schedule. The same 10 to 15 minutes applies after you resume a paused campaign, and after changes to sending accounts take effect.

Why is my Instantly campaign not sending any emails?

Instantly's documented causes are being outside the campaign's sending schedule, the campaign daily limit being reached, per-account daily limits or slow ramp limits being reached, leads being held back for verification or other filters, and sending accounts that are disconnected or paused. Its documentation also points you to the Diagnose button in the campaign's Analytics section to run automatic checks first.

What is the campaign daily limit in Instantly?

Instantly documents the campaign daily limit as the number of sending accounts multiplied by 30. You can raise it in the campaign's Options section or add more sending accounts. Separately, each email account has its own Daily Campaign limit across all campaigns, and Instantly's guidance recommends 30 campaign emails per day per account.

Why does Instantly say no sending accounts are available?

Instantly documents this error as accounts that are assigned to the campaign but cannot send, because they are disconnected, paused, have reached their daily limit, or are restricted by the campaign's slow ramp setting. It asks you to check that account daily limits are not set to 0 and to review the slow ramp settings.

How do I reconnect a disconnected email account in Instantly?

Instantly documents clicking the three dots next to the email account, selecting Reconnect email account, then choosing Connect existing accounts. For Microsoft and Outlook accounts where SMTP was disabled, the documented sequence is to enable SMTP, remove the account from Instantly, wait one hour, then reconnect. Bulk reconnection is an open request on Instantly's public feedback board rather than a shipped feature.

Why did Instantly pause my campaign by itself?

One documented trigger is a high bounce rate, which Instantly describes as recent emails bouncing at a rate typically above 5 percent. The documented fix is to verify the lead list, review the copy with a spam checker, investigate the bounce reasons in Analytics, clean the list, and then resume.

Run the Diagnose check, wait the fifteen minutes, then work down the schedule, limits and accounts in that order. It is a short list and it almost always ends in a setting rather than a bug. And if you would rather the whole outbound loop simply ran, you can try Sistava and hand it to an AI Employee that reports back on what it sent and what came in.

Sources