Skip to main content

LinkedIn Connection Health: What Happens When Your Session Expires

What Skyp does when your LinkedIn session expires — including automatic campaign pause and email notification — and how to reconnect and resume your campaigns.

Written by Alexander Shartsis

Skyp continuously monitors your LinkedIn connection to keep your campaigns running smoothly. If your LinkedIn session expires or becomes inactive, Skyp automatically takes steps to protect your outreach and lets you know so you can reconnect quickly.

What happens when LinkedIn disconnects

When Skyp detects that your LinkedIn session has expired, three things happen automatically:

  • Active campaigns are paused. Any LinkedIn campaigns that were sending will be paused immediately to avoid failed sends.

  • You receive an email notification. Skyp sends a reconnect email to let you know what happened and how to fix it.

  • A reconnect warning appears on the Integrations page. Go to Integrations to see the status and reconnect.

How to reconnect

  1. Go to Integrations in the left sidebar.

  2. Find the LinkedIn section — you'll see a warning that your account needs to be reconnected.

  3. Click Reconnect LinkedIn and complete the sign-in flow in the popup window.

  4. Skyp automatically detects the new connection — the warning clears and the dialog closes on its own.

Resuming paused campaigns

Campaigns paused due to a connection issue are not automatically resumed when you reconnect. This gives you a chance to review them before sending resumes. To resume a paused campaign:

  1. Find any campaigns shown as Paused.

  2. Open the campaign and resume it when you're ready.

Why does LinkedIn disconnect?

LinkedIn sessions can expire for several reasons:

  • You changed your LinkedIn password.

  • LinkedIn automatically expired your session due to inactivity or a security check.

  • You manually signed out of LinkedIn on another device.

Reconnecting takes just a minute, and your campaigns will be ready to resume once you're back.

Did this answer your question?