Why is my LinkedIn campaign stuck or showing wrong numbers?
If your LinkedIn campaign is showing zero activity, the dashboard count doesn't match your LinkedIn inbox, or prospects look stuck in a status that never changes, there are a handful of patterns we know about — most of them now have shipped fixes. This page walks through every common 'stuck' shape, what it looks like, why it happens, and what to do.
1) Auto-paused then auto-resumed near a sending window boundary (fixed Apr 30, 2026)
Symptom: a large group of your prospects show as scheduled with a future send time, but nothing is actually queued for them, so nothing ever sends. Several customers hit this; one had 1,097 of 1,208 active InMail prospects stranded this way on the morning of Apr 30.
Why: when a campaign auto-pauses (for example on a brief LinkedIn account disconnect) and then auto-resumes within minutes, the resume can land just outside your sending window. We correctly moved each prospect's next send to the next valid window, but the matching queued action was left half-finished, so the next sweep treated it as stuck and the prospect was effectively stranded. Nothing new was ever queued for them.
Fix: rescheduling now updates the prospect and the queued action together in one step, and clears the stale in-progress markers. We also re-queued every prospect that had been stranded by the old behaviour. After the fix, your prospects pick back up at the next valid window and run normally. No action needed on your side.
What 'auto-paused' means in general: it's a deliberate safety pattern — account safety always wins. We pause your campaign on a sustained failure rate, a disconnected LinkedIn account, or an upstream outage, to protect the account. Auto-resume re-checks the trigger every 5 minutes; once it clears, your campaign picks up where it left off without burning prospects.
2) Account-card daily counter under-reporting sends (fixed Apr 30)
Symptom: LinkedIn → Accounts shows 'messages sent today: 1' but you can see 24 messages went out in the campaign activity log AND in your LinkedIn inbox.
Why: the weekly counter that actually gates your rate limits was always correct, but the daily tile on the account card under-reported some sends. The campaign activity log and your LinkedIn inbox are always the source of truth.
Fix: every send now updates the daily counter at the same moment it records the send, and a reconciler recomputes the daily figures every 30 minutes so any future drift heals itself. No action needed on your side — just hard-refresh your dashboard.
3) Reply detection looked broken (fixed Apr 30)
Symptom: a prospect replied on LinkedIn but the dashboard still shows them as invited or connected — and Slack / n8n / Zapier reply notifications stopped firing.
Why: replies were being recorded in one place but not mirrored to the place your analytics and Slack alerts read from. The inbound messages still arrived through the polling fallback, but the follow-on effects (reply counter, stop-on-reply, Slack ping) didn't fire.
Fix: the mirror was added, and historical replies were back-filled. Reply stats refresh within about an hour. No action needed on your side.
4) A message step firing on prospects who hadn't accepted yet (fixed Apr 30)
Symptom: prospects showing 'cannot message a non-connection' errors even though the step before was an 'if the invite was accepted' check. The condition step was in the campaign but wasn't holding the message step back.
Why: when the condition hadn't been met yet, it was being read as 'move on' instead of 'keep waiting', so the campaign fell through to the message step before acceptance landed.
Fix: an unmet condition now correctly means 'keep waiting' until it is satisfied or its wait window expires — exactly as you configured it; we never auto-shortcut. After the fix, the message step only fires once the condition is genuinely satisfied.
No action needed on your side — your campaign resumes normally.
5) Phantom accepts (marked accepted without an invite ever being sent — fixed Apr 30)
Symptom: a prospect shows as accepted even though no invite was ever sent from that campaign. One customer's campaign had 150 prospects in this state.
Why: when the same LinkedIn member is enrolled in two or more of your campaigns, an acceptance signal was being applied to all of them — including campaigns that had never actually sent that person an invite.
Fix: an acceptance can now only be recorded against a campaign that genuinely sent the invite. The 150 phantom prospects were reverted so their campaign could re-evaluate from scratch, along with 10 more on another account.
No action needed on your side — your dashboard shows the correct picture after the revert.
6) InMail count showing 0 in dashboards (fixed Apr 30)
Symptom: you can see InMails landing in your LinkedIn outbox and your campaign's 'InMails sent' counter climbing, but a separate 'InMail volume' analytics tile reads 0.
Why: completed InMails weren't being recorded in the feed that the analytics tile reads from. Both paths now record them, and the last 30 days were back-filled.
No action needed on your side.
What to do if your dashboard looks wrong:
- Hard-refresh the page (60-second cache).
- Cross-check ground-truth: campaign-card per-step activity counter is always correct; your LinkedIn inbox/sent items is always correct.
- If still wrong after 1 hour, contact support at [email protected] with your account email and a sample prospect URL — we can reconcile the numbers directly.
What to do if your campaign is auto-paused:
- Check the pause reason on the campaign card. The common ones are: LinkedIn account disconnected, high failure rate, paused manually, and subscription lapsed.
- LinkedIn account disconnected: open LinkedIn → Accounts, click Reconnect on the affected row, complete the LinkedIn login. Auto-resume picks up within 5 minutes.
- High failure rate: review the recent errors for that campaign. The most common cause is messages firing before acceptance (point 4 above) — check that your steps have a 'wait for acceptance' or 'if the invite was accepted' check BEFORE any message step.
- Paused manually: click Resume.
- Subscription lapsed: settle the outstanding invoice. That is the only thing that clears this one, and the campaign resumes on its own within about a minute afterwards.
Account safety (always wins): every fix above works on data we already hold — no extra LinkedIn calls, no rate-limit risk, no account flags. The engine respects per-account daily and weekly limits, sending windows, and timezone — exactly how you configured them. We never auto-shortcut, never skip steps, never burn prospects to 'help'.