My campaign is stuck or not sending

My campaign is on but no messages are going out, or recipients are stuck on a step that should have triggered.

CLIENT-ONLY · Troubleshoot

Likely causes

Campaign is OFF. New campaigns default to OFF. Check the toggle.
No recipients. A campaign with zero recipients sends nothing. Check the Recipients tab.
Sender disconnected. If Gmail, Outlook, LinkedIn, or WhatsApp dropped, the campaign pauses. Check Settings, Accounts.
Daily limit reached. New email accounts cap at 50/day, then wait until tomorrow. Same for LinkedIn (35 connection requests/day; message and InMail caps vary by product: Classic, Sales Navigator, or Recruiter) and WhatsApp (100 messages/day).
Provider throttling. If a provider starts rejecting sends (bounce rate above ~3%), Wiggli pauses and preserves state.
Step delay not reached. A 3-day delay means recipients sit on a step for three days. That’s intentional.
Missing data blocks the step, it does not skip ahead. The sequence runs its steps in order. A recipient who lacks the data a step needs (no email for an email step, no LinkedIn URL for a LinkedIn step, no phone for a WhatsApp step) waits at that step and does not jump to a later channel. One missing data point holds a recipient behind every step after it, which is why active counts drop sharply between steps. Reveal or complete contact data before launching, and lead with the channel most of your list is reachable on.
Waiting for a specific email type. An email step targets a particular email type (personal or work), chosen when you added the profiles to the campaign, and that choice can’t be changed afterwards. A recipient who only has the other type stored waits, showing This recipient is waiting for the email type selected for this campaign. Revealing contacts at project level doesn’t automatically make everyone ready: the campaign needs the specific type it was set to. Fix it by bulk-revealing the missing type from the project (Search missing), or run those profiles through a LinkedIn-only campaign, which needs no reveal at all.
The error matches the channel, not the campaign. Read blocking errors against the channels your campaign actually uses. On a LinkedIn-only campaign, a personal email needed message is noise, the campaign keeps running on the LinkedIn URL alone. On an email campaign, the same message is the blocker.
Using the Wiggli default sender. The Wiggli Email default sender is a legacy fallback, not the normal setup. It has weaker deliverability and returns little delivery confirmation, so a campaign on it can show everything as Sent with 0 delivered. Connect your own Gmail or Outlook account and send from that.
Warm-up phase. New accounts ramp slowly; day 1-2 is 50 emails total, not per campaign.
Working-hours filter. If sends are restricted to business hours and you’re outside that window, they pause.

Solution

Confirm the campaign toggle is ON.
Open Recipients. Confirm profiles are Active or In progress.
Open Settings, Accounts. Confirm every sender shows Connected.
Open campaign analytics. Compare Sent today to the daily cap for that channel.
Check for an account-level error (e.g. “Gmail authentication expired”).
Review the sequence. A multi-day delay is a deliberate wait, not a fault.
Give analytics an hour or two. Sends run in the background and the numbers follow with delay; judge the Step performances section rather than the overview counters.
If the campaign predates the July 2026 campaign rework, use the Retry banner at the top of the campaign, or duplicate the campaign (the icon next to the trash icon) so it runs on the new engine with cleaner tracking.

What the blocked reason means, and what to do

Open the stuck recipient in the sequence details and read its status and blocked reason. A recipient on Pending is waiting for required data before it can continue. A blocked step falls into one of three groups.

Account issue (reconnect, then it retries on its own).

Account Disconnected or Account Expired. The sender account for that step dropped or needs a fresh login. Go to Settings, Accounts, reconnect it, and confirm it shows Active. Wiggli then clears the block and the step retries on its own.

Waiting on the candidate or a limit (resolve it, then it retries on its own).

Connection Pending. Waiting for the candidate to accept your LinkedIn connection request.
Connection Not Accepted. They didn’t accept. Reach them on another channel, or lead with a connection request next time.
LinkedIn Profile Not Found. The LinkedIn URL doesn’t resolve to a person profile. Check it.
InMail Credits Exhausted. The LinkedIn account is out of InMail credits. Wait for the reset, or send from another LinkedIn account that has credits.
LinkedIn Rate Limited or WhatsApp Rate Limited. The daily cap is hit. Sending resumes when the limit resets. Rate-limited recipients are queued and typically retry within an hour or two.
Sending resumes soon. Hover for Reprise scheduled for [date]. Sending is paused by a limit and resumes automatically at that moment. Nothing to fix.
Send Failed. A one-off failure. It retries later. Contact support if the same one keeps repeating.

Missing or bad data (fix the data, then retry the recipient).

Email Missing. Add or reveal an email for that recipient.
Email not reachable. The address is invalid or likely to bounce. Reveal a better one or use another channel.
Phone Number Missing. Add or reveal a phone number.
Invalid Phone Number. Fix the format to international, for example +14155550100.
LinkedIn URL Missing. Add or reveal the LinkedIn profile URL.

Reconnecting an account never fixes a data, credit, or limit block. If a step is still stuck after you reconnect, look for a second reason in the list above.

A habit that prevents most of these blocks: before enrolling, ask the project Co-pilot to filter out the profiles without a personal email (or whatever the campaign’s first channel needs) and enroll only that set. You launch with a list that can actually run.

“Sent” but “0 delivered”, is it actually broken?

Usually not. Sent means Wiggli fired the message. Delivered only registers when a confirmation signal comes back: a delivery receipt, open, click, or reply. No signal does not mean no send. This reads emptiest on the Wiggli default sender, which returns almost no confirmation data, so a campaign there can show Sent with 0 delivered even though the messages went out. Connect your own mailbox for real delivery and open tracking, and judge cold email on reply rate, the reliable signal.

When to escalate

If the campaign is on, recipients are active, senders are connected, caps aren’t reached, and sends still aren’t happening, contact support with: campaign name, a specific stuck recipient, expected vs actual send time, and any error in the analytics.

Still stuck?

Your customer success manager reads faster than any search bar.

Get help