How does WarmySender redistribute schedule when I disconnect?
When a LinkedIn account disconnects (LinkedIn rotated your session token, you triggered a 2FA prompt, or the account was paused for any reason) WarmySender holds your campaign schedule in place — but it doesn't burst-send the backlog the moment you reconnect. This guide explains how the platform redistributes prospect schedules to keep your account safe.
The core invariant: account safety always wins
LinkedIn's anti-abuse signal-set heavily weighs 'unusual burst activity after a quiet period' as a strong automation signal. A disconnect of any duration followed by an immediate flood of messages or invites looks indistinguishable from a botted-account pattern, regardless of whether the activity is real or automated. The platform's design constraint is: never burst after a reconnect, ever.
What happens during a disconnect
- Sends that were already in flight when the disconnect occurred are released cleanly and put back in the queue, so nothing gets stuck half-finished.
- Future-scheduled prospects whose next action falls during the disconnect window are NOT immediately moved. They stay on their existing schedule.
- The campaign auto-pauses because its LinkedIn account is disconnected, so it doesn't try to send while the account is dark.
What happens during a reconnect
- The account flips back to Connected and re-registers for LinkedIn's real-time notifications.
- The auto-resume sweeper resumes campaigns paused for the disconnect within ~5 minutes.
- Prospects whose next action came due during the disconnect are moved forward to the next valid sending window. That move respects your active days, sending window start and end, timezone, and time-randomisation setting — exactly the same settings the campaign was authored with.
- A small random offset (0-30 minutes) is added per prospect during redistribution so prospects that would otherwise share a scheduled minute are spread out.
Why this can sometimes look like 'all my prospects are scheduled for next Monday'
If your campaign's active days are restrictive (e.g., Monday and Thursday only), and the disconnect spanned multiple weekdays, the next valid sending window for a large block of prospects might land on the same Monday. The platform's drift reconciler now skips imminent-valid-day rows (next-action within 24h AND on a valid weekday) so genuinely-correct schedules don't get re-distributed unnecessarily — but if your chosen schedule is Monday and Thursday and the affected prospects all land in the same Monday window, that's the schedule doing what you set it to do, not a bug.
If you ever see hundreds of prospects scheduled for the same single Monday and that's NOT what you intended, please email support — we shipped a fix specifically to address an over-shift pattern that produced this exact symptom on May 2 2026, and we can redistribute the affected prospects for you.
The per-account ramp survives reconnects
Your 4-week LinkedIn safety ramp (10 invites/day → 50 invites + 150 messages/day) is per-account, not per-campaign, and it accumulates across disconnects. Reconnecting after a 24-hour disconnect doesn't 'reset' your ramp — you pick up from where you left off, slightly delayed. This is intentional: the ramp is what keeps your account safe.
Does the platform ever speed up after a reconnect?
Never. The platform always defers, never accelerates. If your dashboard shows a higher per-day cap than what's actually being sent, that's the daily cap (the upper bound) — not a target. Actual throughput respects the campaign's per-prospect timing, the account's ramp schedule, the per-account daily/weekly limits, and the per-account hourly burst limit our integration partner enforces. Each gate applies independently. Worst case after a reconnect: a few rows are deferred slightly longer than they would have been if the account had stayed connected. Best case: the schedule catches up smoothly within the next few sending windows.