Why are my LinkedIn prospects still paused after I reconnected?

What this page is for

If your LinkedIn account in WarmySender Settings shows the green Connected pill but a portion of your campaign prospects still appear in a "paused" state — particularly after a long disconnect window — this page explains what's happening and what we automatically do about it. WarmySender is a 4-pillar outreach platform — Cold Emailing, Email Warmup, LinkedIn Outreach, and Multichannel sequences. This page is part of the LinkedIn Outreach pillar troubleshooting set.

Why prospects pause when your account disconnects

When the LinkedIn account behind a campaign disconnects (OAuth token expired, account flagged for verification, transient upstream blip that exceeds our 2-hour tolerance window, etc.), our scheduler does the safe thing first: it flips every active enrollment on that account to a soft-pause state and pauses the campaign at the workflow level. This is intentional. Our engine errs on the side of refusing to send when state is uncertain — a banned LinkedIn account is unrecoverable. We never push messages or invites through an account whose connection status is anything other than Connected.

The trade-off is that the soft-pause is a holding pattern: those enrollments stay in place until the account is healthy again. The question this page answers is: what wakes them back up?

The auto-resume cycle (15-minute cadence)

Two complementary mechanisms wake paused enrollments after a reconnect:

1. Webhook-time resume (immediate, when the connect signal arrives)

The instant our LinkedIn integration delivers a connect signal for a previously-disconnected account, our handler runs a single-transaction resume pass. This pass does three things at once: it flips paused enrollments back to active on the now-connected account, resumes any LinkedIn campaign that was paused because of the account issue or disconnect, and re-points enrollments belonging to an old account record (the case where you reconnected by adding a NEW account instead of refreshing the same one) to the new connected record. When the signal arrives reliably, this is the entire story — your prospects start sending again on the next scheduler tick (within roughly five minutes), bound by all the usual gates: per-account daily/weekly caps, sending window, ramp week, action cooldown.

2. Periodic auto-resume sweep (15-minute backstop, shipped May 7, 2026)

Connect signals are best-effort by design. They can be lost in transit, queued past their expiry, fired before the account is fully connected, or — most commonly in practice — reach our endpoint while the user is mid-flow re-adding the account through a different account identifier than the one their old enrollments point at. To close that gap, on May 7, 2026 we shipped a 15-minute periodic sweep that runs purely against our own data (zero new LinkedIn API calls), looks for paused enrollments whose attached account is currently Connected — directly OR via a workspace + LinkedIn-member sibling-account match (the reconnect-by-new-account case) — and flips them back to active under a running campaign. The sweep enforces two caps to prevent stampede on a freshly-reconnected account: 200 enrollments per account per tick and 2,000 enrollments platform-wide per tick. Resumed enrollments are spread across a 0-15 minute jitter window so the scheduler isn't asked to drain hundreds of newly-active rows in a single instant.

What you see in the dashboard

If your account just reconnected, the typical user experience is:

  1. Minute 0: click the Reconnect button in Settings → flow completes → account flips to Connected.
  2. Within ~1 minute: the connect signal lands → our resume handler runs synchronously. Most enrollments flip back to active and the campaign resumes.
  3. Within ~15 minutes: the periodic sweep runs. Any enrollments the connect signal missed (cross-account reconnects, lost connect signals, edge-case campaigns that were paused for an unrelated reason and you've since manually resumed) flip back to active here.
  4. Within ~30 minutes: the scheduler's normal flow has picked them up and the first sends fire — bound by your account's ramp week, daily cap, sending window, and per-action cooldown. Account safety always wins: even after resume, every existing gate applies, so a 4-week-old account that just reconnected won't suddenly attempt 100 invites in one minute.

When the auto-resume does NOT apply

Three deliberate exclusions:

If you have a large backlog of paused prospects

The 200-per-account-per-tick cap is deliberate: it spreads the resume work across multiple ticks so one freshly-reconnected account with thousands of paused rows doesn't release them all at the same instant (which would compound with the scheduler's ramp gate to produce a small but undesirable load spike). At 15-minute cadence and 200 rows per tick that's 800 enrollments per hour per account — enough to drain a several-thousand-row backlog within a day without operator intervention. If you have a much larger backlog (the platform-wide May 7, 2026 audit found a 102,000-row cohort on a single workspace) and you want it drained faster, our support team can run a one-shot heal pass with a higher per-run cap, re-runnable as many times as needed to drain. Email hello@warmysender.com if you want it accelerated.

Common questions

Did I lose any prospects from the disconnect?

No. The paused state is a holding pattern, not a delete. Every prospect, every step they had completed before the disconnect, and every step still ahead of them is preserved. When the account reconnects and the auto-resume sweep flips them back to active, the engine resumes from exactly where they left off. We preserve each prospect's current step position by design, so already-invited prospects don't get duplicate invites on resume.

Will resumed prospects break my account's daily limit?

Never. The auto-resume sweep ONLY flips internal state — it does not enqueue any LinkedIn actions itself. Once the prospects are active again, the scheduler's normal flow picks them up and applies every existing gate: per-account daily and weekly caps, ramp week, sending window, per-action cooldown, and an atomic action reservation gate. A 4-week-old account that just reconnected will still only send up to its 4-week-ramp ceiling that day. Account safety always wins — even after a resume.

How long does it take from reconnect to first send?

Typical experience: under five minutes for the first prospect to send (webhook-time resume + scheduler's one-minute tick). Outliers extend if the connect webhook is lost in transit (auto-resume sweep catches up within 15 minutes), if the campaign was also paused for an unrelated reason (resume the campaign first), or if the account is in its first ramp week (sends are intentionally throttled for the first 4-6 weeks of any new connection — this is a deliberate safety guardrail, not a bug).

Why didn't this work before May 7, 2026?

It mostly did — the immediate resume on reconnect signal has been in place for months. The gap was a class of edge cases where the signal either didn't arrive reliably or arrived against a different account record than the one your old enrollments pointed at. The May 7 sweep adds member-based matching as a backstop: if any account in your workspace tied to the same LinkedIn member is connected, your old enrollments under the previous account record also flip back. Pre-May 7, those were silently stuck — a small portion of the platform's paused-prospect total, but real lost throughput for affected workspaces.

Can I see when the auto-resume ran on my account?

Yes — the LinkedIn campaign event log surfaces the resumed status flip at the per-prospect level under the prospect's history pane, including the timestamp when the auto-resume moved each prospect from paused back to active. Each tick also records an aggregate summary (number of accounts processed and number of prospects resumed).

What if I want to disable the auto-resume?

Contact support if you need the auto-resume sweep turned off for your workspace. We don't recommend disabling it — the paused-after-disconnect state is a holding pattern, and without auto-resume the only way to drain it is a manual sweep after every reconnect event.

Account safety

Zero new LinkedIn API calls. The auto-resume sweep is purely internal — read paused enrollments, flip them back to pending, log the change, done. We never re-poll LinkedIn to "verify" the connect status: we trust the connection status we already track for the account, which is maintained by our existing reconnect-signal handling and protected by the platform's mass-disconnect monitor and temporary-safety-mode guard.

The 200-per-account / 2,000-fleet caps are a stampede guard, not an account-safety primitive. Account safety is enforced at the next layer down by the action reserver, ramp-week gate, sending-window clamp, per-action cooldown, and per-account daily/weekly caps — all of which apply equally to a freshly-resumed enrollment and a never-paused one. LinkedIn account safety always wins: even when the auto-resume happens, every gate downstream still applies.

Still seeing prospects stuck in paused state more than 30 minutes after a clean reconnect? Email hello@warmysender.com with the account display-name and one or two stuck prospect URLs — we'll cross-check against the auto-resume sweep log and either flush them manually or open a follow-up.