How to Fix "Disconnected by LinkedIn" and Other Account Disconnection Errors

An account disconnection error ("Disconnected by network," "Disconnected by LinkedIn," "Disconnected by Instagram," "Please provide a new LinkedIn session cookie") means your Phantom authenticated successfully but was cut off mid-run, usually because the platform detected suspicious activity and triggered its safety mechanisms. To fix it: reconnect your account from the Phantom console, then reduce your activity before relaunching (fewer actions per launch, more spacing, start at 50–70% of recommended limits). If disconnections are frequent, pause for one to two weeks before resuming.

If your error mentions an expired or invalid session cookie rather than a disconnection, see How to Fix "Expired" or "Invalid" Session Cookie Errors instead.

Why you're seeing this

Your automation may show one of these messages during a run:

"Disconnected by network"
"Disconnected by LinkedIn" / "Your LinkedIn session has been disconnected"
"Disconnected by LinkedIn. Consider lowering activity levels or taking a short break" / "Please provide a new LinkedIn session cookie"
"Disconnected by Instagram" / "Your Instagram session has been disconnected"
Or a similar disconnection message from another platform

This error means your Phantom authenticated successfully at the start of the run, but the connection was cut while the automation was running. The platform detected activity that triggered its safety mechanisms.

Common causes include:

Too many actions performed in a short period, the most common trigger.
Running multiple automations simultaneously on the same account, including Phantoms chained through Workflows.
A sudden spike in activity after a period of inactivity.
An IP address change during the run.
The platform flagging your account for unusual behavior.

How to fix it

Reconnect your account

Go to the PhantomBuster Dashboard and locate the automation showing the error.
Click on the error to open the Phantom console.
Inside the console, click Resolve.
You'll be redirected to the Setup page. Click Re-connect next to your account.
Save your updated setup.

If you need step-by-step guidance on reconnecting your account, see:

Reduce your activity before relaunching

Reconnecting alone won't prevent another disconnection if your activity level is what triggered the first one.

Before relaunching, reduce the number of actions per launch in the Behavior step and space out your launches in Launch Settings. If disconnections happen regularly, consider pausing all activity for up to one to two weeks to let your account recover and move away from the platform's radar before starting again.
When you resume, scale your activity gradually, start at 50–70% of the recommended limits and increase slowly over time.
→ See Automation Rate Limits by Platform and Popular Phantom and Best Practices for Social Media Platforms Automation for guidance.
If you're running multiple Phantoms on the same account or chaining Phantoms through Workflows, stagger your launches or consolidate where possible. Compounding activity across Phantoms is a frequent cause.
If you're using Facebook Phantoms or are on an unstable or frequently changing IP address, consider setting up a proxy for a more consistent connection.
→ See Use a Proxy to Fix Login Issues or Get Location-based Results.

Frequently asked questions

What does "Disconnected by LinkedIn" mean?

Your Phantom connected successfully at the start of the run, but LinkedIn cut the connection while the automation was running. It usually means LinkedIn's safety systems flagged the activity as suspicious.

How is this different from an expired session cookie?

An expired cookie means your session timed out before the Phantom could use it. A disconnection happens mid-run, the session was valid at launch but was terminated by the platform. The fix for disconnections requires reducing activity, not just reconnecting.

Will reconnecting my account fix the problem permanently?

Not on its own. If you relaunch at the same activity level, you'll likely get disconnected again. Pair reconnection with reduced action volume and better pacing.

How long should I pause if disconnections keep happening?

One to two weeks of full inactivity is the usual recommendation. When you resume, start at 50–70% of the recommended rate limits and scale up slowly.

Do I need a proxy?

Consider one if you're using Facebook Phantoms, if your IP changes frequently, or if you're running from an unstable connection.

Can running multiple Phantoms on the same account cause disconnections?

Yes. Running multiple automations simultaneously on the same account, including Phantoms chained through Workflows, is a common trigger. Stagger your launches or consolidate Phantoms where possible.