Reconnecting a LinkedIn account can restore the sender without restarting its campaign. It can also release waiting steps automatically, depending on the tool. Before clicking Reconnect, note the affected sender, the campaign's pause state, and a sample lead's next action. Afterward, verify those three records again before letting the queue run. Vendor help pages document different restart rules; the word ‘connected’ alone cannot tell you what will send next.
The sender and the campaign recover on different clocks
Emelia says it pauses campaigns when a sender disconnection is confirmed. A reconnection within 15 minutes restarts them automatically; a later reconnection requires a manual campaign restart. Skyp also pauses active campaigns when its connection expires, but says reconnecting does not resume them. By contrast, useArtemis says waiting LinkedIn steps retry after reconnection while steps on other accounts and email can continue. These are vendor-documented rules for those products, not a general LinkedIn behavior.
A browser-based connection creates another state to check. Distro says a campaign waits when its Chrome extension stops checking in and picks up when the browser returns. If the operator explicitly paused the account, Distro requires Resume. A dashboard may therefore show an intact campaign while its sender session, browser, or campaign switch is the part that needs attention.
Sources: Emelia: LinkedIn account disconnections, Skyp: expired LinkedIn session, useArtemis: reconnect a LinkedIn account, Distro: LinkedIn account and browser connection
Check LinkedIn itself before repairing the tool
Open the affected profile in LinkedIn and look for a security challenge, invitation restriction, or account notice. A vendor's Disconnected label does not identify which of those happened. useArtemis, for example, lists Restricted by LinkedIn separately from a lost connection and directs the account holder to resolve the platform prompt first. Record the exact notice before changing the vendor setup.
LinkedIn says third-party software that scrapes, modifies, or automates website activity is prohibited and can lead to account restriction. Reconnecting another session or rotating in a different sender is not a remedy for a platform restriction. If the account is restricted, follow LinkedIn's own recovery instructions and keep the affected campaign stopped while the account owner decides whether that workflow should continue at all.
Sources: useArtemis: reconnect a LinkedIn account, LinkedIn: automated activity, LinkedIn: account restrictions
Take a checkpoint before queued work can move
If the product allows it, pause the affected campaign before reconnecting. Write down the LinkedIn profile, campaign, last completed action, and next due action for two or three affected leads. Check whether any of those people replied while the tool was offline. Compare a purportedly sent message with the native LinkedIn conversation before pressing a retry or resuming a sequence. The aim is to distinguish work still waiting from work the tool has not yet reflected in its report.
Reconnect the same LinkedIn profile through the product's documented Reconnect path. Emelia warns that its extension can attach whichever LinkedIn profile is open in the browser; useArtemis says removing an account and adding it again creates a new connection that must be selected in campaign steps. Confirm the profile identity and connected status, then inspect the campaign's pause state and a lead's next step. A Connected badge is one checkpoint, not the finish line.
Release one supervised test step, if the tool permits that level of control, and verify the native outcome before allowing the rest of the queue to continue. If the tool cannot expose the next scheduled step or the sender that owns it, keep the campaign paused and ask its support team for the event trace. This is an operator check, not a claim that every product offers a single-step test control.
Sources: Emelia: LinkedIn account disconnections, useArtemis: reconnect a LinkedIn account
Do not treat a spare sender as an automatic replacement
In useArtemis's rotating campaigns, leads assigned to a disconnected account wait for that account. Removing it from the rotation can reassign them at their next LinkedIn step, but the vendor warns that the new sender may not be able to message a person who accepted the original sender's invitation. That is a relationship problem, not merely a capacity problem. Other tools may assign work differently, so ask for a lead-level sender record before moving a backlog.
The same vendor notes that two accounts can contact one lead across separate campaigns. Check the contact's existing conversation and do-not-contact state before copying a stalled list into a new campaign. If the original sender cannot return, plan the handoff as a new outreach decision with a named account owner rather than assuming the sequence can continue unchanged.
Make the restart rule a buying test
In a trial with consenting internal accounts, disconnect or pause one test sender using the vendor's supported controls. Record whether the tool alerts an owner, freezes only that sender's leads, preserves their step positions, and resumes automatically or waits for an explicit command. Then reconnect the same profile and check the next due action against the native LinkedIn record. Repeat the question for a payment pause and an operator pause; useArtemis documents a different restart path after a subscription lapse.
Choose a product only after its recovery behavior fits the team's approval process. Automatic continuation can be useful for a short outage, but a long interruption leaves old messages waiting for a fresh decision. Manual resume gives an operator that review point, provided the product shows enough lead and sender detail to make it meaningful. The published help pages establish what vendors say today; only a controlled trial establishes what the team's plan and configuration actually do.
Sources: useArtemis: reconnect a LinkedIn account, Emelia: LinkedIn account disconnections, Skyp: expired LinkedIn session