A prospect accepts a connection request, enters a follow-up sequence, then removes the sender before the next message is due. LinkedIn says the removal ends the first-degree connection and gives the removed member no notification. The campaign's earlier ‘connected’ state can therefore be stale. A tool may stop the sequence, skip the message, or surface a failed task; its own event record must settle which happened. Do not assume that a message scheduled while the connection existed is still eligible to send.
The due date does not preserve message eligibility
LinkedIn says a removed connection is no longer first-degree. Its current messaging help describes ordinary direct messages as messages to connections; message requests for certain nonconnections and Premium InMail are separate routes. That distinction matters even if the old conversation remains visible. The help pages we checked do not establish that an existing thread lets every former connection receive another ordinary message.
The relationship is also sender-specific. If one teammate remains connected while the assigned sender was removed, the assigned sender's queued message still needs its own eligibility check. A lead list's ‘connected’ label may describe an earlier import or another account. Record the sender and the current native LinkedIn relationship before deciding what to do with the queued step.
Sources: LinkedIn: Remove a connection, LinkedIn: Send messages to connections
A stopped, skipped, or failed step means different work
SocialScalr says its sequences stop when a lead disconnects and record that reason in the lead timeline. That is a vendor claim; its public page does not show how quickly the change is detected. meetergo documents a different observable result for a message addressed to a nonconnection: the campaign skips the message and moves on. GetSales lists ‘not connected to lead’ among failed message-task reasons. Its example concerns a pending invitation, so it shows a possible failure state, not proof of how GetSales handles a connection removed after enrollment.
Ask the vendor where a removed connection appears: lead status, skipped-action log, failed-task counter, or a stop reason. Then ask whether later steps are cancelled. A skipped message that leaves the lead active could allow a later action to run. A failed task with a retry button can also be dangerous if an operator restarts it without rechecking the relationship. Inspect the next scheduled action, not only the most recent error.
Sources: SocialScalr: Sequences, meetergo: Why a LinkedIn action was skipped, GetSales: Campaign troubleshooting
Test the transition with a consenting pair
Use two internal LinkedIn accounts whose owners agree to the test. Confirm that the intended sender and recipient are first-degree connections. In a paused test campaign, record the sender, recipient, queued message, due time, current relationship, and the tool's lead state. Have the recipient remove that connection in LinkedIn. LinkedIn says the removed member receives no removal notice, so the operator should not expect a notification to repair the campaign state.
Before the due time, inspect the sender's native LinkedIn view and the tool's lead record again. Keep the campaign paused if you cannot see a current relationship check or the next action. If the test product can safely run a supervised step under your policy decision, compare the resulting event with the native sent history: stopped before send, skipped, failed, sent, or unknown. Record whether any later step remains queued. This is a proposed test, not a result we obtained from a live vendor account.
- At enrollment: which LinkedIn account owns the connection and which account will send?
- Before the step: when was relationship status last checked, and what does the native account show now?
- After the step: is there a stop, skip, failure, or confirmed send, and what remains queued?
Sources: LinkedIn: Remove a connection, meetergo: Why a LinkedIn action was skipped
Hold the contact until the next route is chosen deliberately
A removed connection, an unanswered invitation, a blocked sender, and a reply are different events. A retry for ‘not connected’ is reasonable only after the operator knows why the relationship changed and whether further contact is appropriate. Do not automatically turn a removed connection into a new invitation or an InMail. Review the contact's prior conversation, any opt-out or suppression record, and the sender's current native options first. If the contact appears to have chosen to disconnect, leaving them out of the campaign is the prudent default.
For a small list, a person can review native LinkedIn state and write eligible messages manually. OutreachGenie's current pricing describes a Free workspace with 80 outreach actions and 500 new prospects a week; visits, lists, and flows are unlimited. Those are product-side limits, and LinkedIn's own limits still apply. Its pricing page does not verify removed-connection detection, so do not treat the workspace as a substitute for the transition test above.
Sources: LinkedIn: Send messages to connections, OutreachGenie pricing
A vendor stop rule does not settle LinkedIn's rules
LinkedIn says it does not permit third-party software that scrapes or automates activity on its website and warns that accounts using prohibited tools may be restricted or shut down. A vendor's stop-on-disconnect claim describes its own product behavior, not LinkedIn approval or a lower-risk way to automate. Decide whether to use any such tool before connecting an account. The native relationship check remains useful even when the team chooses manual sending only.
Disclosure: we also make OutreachGenie.