Reconnecting your LinkedIn account after a platform update
From time to time we ship platform-level updates that improve sync speed, delivery reliability, and account-state guarantees. After certain rollouts, LinkedIn accounts connected to WarmySender need a quick re-authentication so the new platform components can pick up the session. If you see an amber 'Reconnect needed' banner at the top of LinkedIn → Accounts, this guide is for you.
Why reconnects sometimes happen after a platform update
WarmySender connects to LinkedIn through Unipile, an authentication and orchestration partner. When we upgrade core components — for example, our queue runtime, our LinkedIn worker pool, or the way we register accounts on Unipile's side — accounts that were connected on the old infrastructure can become 'orphaned' relative to the new layer. Their actual LinkedIn session is fine; what's stale is the link between WarmySender and Unipile for that specific account. The fastest, safest fix is for you to re-trigger the auth handshake so a fresh, clean record is created on the new infrastructure. This is intentional — silently rebinding accounts in the background is exactly the pattern LinkedIn flags as suspicious. A brief, user-initiated reconnect keeps your account in great standing. We will only ever send you a reconnect email when the change is rolling out platform-wide; ad-hoc disconnects (LinkedIn-side session expiry, password change, 2FA reset) are covered in our separate 'Why does my LinkedIn account show as disconnected?' guide.
Who needs to reconnect
Anyone whose LinkedIn account on the LinkedIn → Accounts page shows the amber 'Reconnect needed' alert. If the page is fully green for every account, no action is needed on your end. If even one account is amber, click Reconnect on that row to clear it. Multi-account workspaces should reconnect each affected account individually — it takes about 30 seconds per account.
How to reconnect (4 steps, ~30 seconds)
1) Open WarmySender and go to LinkedIn → Accounts in the sidebar. Affected accounts show an amber 'Reconnect needed' alert with a primary 'Reconnect Account' button. (Screenshot: an amber banner at the top of the page reading 'Reconnect needed — N LinkedIn account(s) require re-authentication' followed by per-row alerts on each affected account.)
2) Click 'Reconnect Account' on the row. You'll be routed to a hosted re-authentication page. No credentials are shared with WarmySender directly — Unipile handles the auth securely via LinkedIn's official OAuth-style handshake.
3) Confirm your LinkedIn login. If 2FA is enabled, enter the code. If LinkedIn shows a security challenge or CAPTCHA, complete it as you would any other LinkedIn login. The whole thing should take ~15-20 seconds.
4) Return to WarmySender. The status pill flips from amber 'disconnected' to green 'connected' within seconds. The aggregate banner at the top of the page disappears once every affected account is reconnected. (Screenshot: green 'Connected' status pill alongside the account row, and the amber top-of-page banner gone.)
What happens to my campaigns during reconnection
The moment a LinkedIn account becomes disconnected, every campaign attached to it is auto-paused with reason 'account_disconnected' or 'linkedin_account_disconnected'. Each affected campaign shows a small hint on the campaign card and detail page: 'Will auto-resume after LinkedIn account reconnection.' Prospects keep their exact place in the sequence — nothing is dropped, nothing is reset, no step is skipped. As soon as you complete the reconnect, the platform's failure-rate window resets for that account and the next scheduler tick (within ~5 minutes) automatically resumes the paused campaigns. You do not need to manually click Resume on each one. Account safety always wins: even on resume, sends respect your daily / weekly LinkedIn caps, your sending window, and your active days — there is no burst catch-up of held-back invites.
If a campaign was paused for any OTHER reason at the same time (manual pause, high failure rate from before the disconnect, or a different downstream issue), it may still need a manual Resume from its settings page after reconnection. If you click Resume and it immediately re-pauses, contact support — that signals a stale failure window that needs manual reset.
FAQ
Q: Will I lose my prospects or audiences?
A: No. Reconnecting only refreshes the link between WarmySender and your LinkedIn session. Your prospects, audiences, conversations, campaign sequences, and historical metrics are all stored on our side and are untouched by the reconnect.
Q: Will my campaigns restart from the beginning?
A: No. Campaigns resume from the exact step each prospect was on at the time of the disconnect, including any 'wait for acceptance' or 'wait N days' delays that were in flight. There is no reset and no re-enrollment.
Q: What if reconnect fails or the status doesn't update?
A: Wait 30-60 seconds for Unipile's webhook to land, then click 'Sync Status' from the account's three-dot menu. If the status still shows disconnected after a manual sync, the auth flow may not have completed — close any in-progress reconnect tab and try the reconnect button again from a fresh browser tab. If it still fails after a second attempt, email hello@warmysender.com with your account email and we'll look at the specific row.
Q: How often do I need to reconnect?
A: Rarely. Platform-update reconnects are infrequent — usually only after meaningful infrastructure rollouts. Ad-hoc reconnects are also rare and are typically driven by LinkedIn (password change, 2FA reset, idle session, IP region change). Accounts in good standing on Premium / Sales Navigator can go months without ever needing a reconnect.
Q: Is my LinkedIn account safe? Will this trigger a flag?
A: Yes, your account is safe. The reconnect uses LinkedIn's official authentication flow via Unipile — the same secure handshake any approved tool uses. We never store your LinkedIn password, never bypass 2FA, and never reuse stale tokens. Reconnect after a platform update is a routine, low-stakes action that LinkedIn treats exactly like any other login from your normal IP/device.