Why does my LinkedIn campaign say "Unresolvable URL" for prospects I know are valid?

Q: Why does the banner say 'your session has lapsed' instead of just 'reconnect'?

Because naming the cause helps. A blanket 'Reconnect' with no explanation invites the question 'is something genuinely broken on WarmySender's side?' — and the honest answer is no, your LinkedIn session lapsed for one of a small number of well-known reasons. That precision lets you decide whether to investigate the reason (IP change, security challenge, etc.) or just reconnect and move on. Most customers reconnect and move on; the few who want to investigate now have the information.

Q: Is 'Unresolvable URL' the same as 'Skipped' on my campaign?

Closely related but not identical. 'Skipped' is the broader panel label; 'Unresolvable URL' is one specific reason a prospect can land in that panel. The new account-level reconnect banner replaces the per-prospect 'Unresolvable URL' chips when WarmySender detects the cause is your session, not a genuine per-prospect issue. See the companion page 'Why was my prospect skipped — no LinkedIn URL' for the per-prospect case.

Short answer

Almost always your LinkedIn session has lapsed. The prospects haven't been skipped — your account needs one reconnect click. Once you reconnect, the campaign auto-resumes and every prospect that failed during the lapsed-session window is re-attempted automatically. No re-import or manual action is needed.

The label you see is the same regardless of the underlying cause ("Unresolvable URL"), but the cause matters because it tells you which fix to apply. In the typical case, every prospect on the campaign starts failing at roughly the same time — that's the account-level fingerprint. If only a handful fail and the rest send normally, that's the profile-level fingerprint (vanity URL changed or profile deleted), which is a different fix.

WarmySender is a 4-pillar outreach platform — Cold Emailing, Email Warmup, LinkedIn Outreach, and Multichannel sequences. This page is part of the LinkedIn Outreach pillar.

The three real causes

Three independent things can produce an "Unresolvable URL" outcome on a LinkedIn campaign send. Knowing which one you're seeing tells you which fix applies.

Account-level: your LinkedIn session has lapsed (most common)

LinkedIn auto-logged out the session WarmySender uses to look up prospects. This is the cause in the vast majority of cases where many prospects on the same campaign all start failing at once. The session is independent from your browser session — you can be logged in on linkedin.com in Chrome while the session WarmySender uses to act on your behalf has gone stale.

Common triggers for an account-level session lapse:

IP change. Connecting from a new ISP, a different VPN exit, a new office, or a different country can cause LinkedIn to invalidate the session for security.
LinkedIn security challenge. A "Was this you?" interstitial, a phone-verification, or a captcha-style challenge during normal browser use can quietly invalidate background sessions even after you complete the challenge.
Extended idle. Sessions older than approximately 30 days routinely rotate; LinkedIn does not document the exact interval and we don't try to predict it — we just detect the lapse and surface the reconnect prompt.
Password change or 2FA reset. Both invalidate every session associated with the account on LinkedIn's side.

Fix: open Settings, go to your LinkedIn accounts, and click Reconnect LinkedIn. The reconnect itself takes about thirty seconds. Once it lands, WarmySender automatically re-attempts every prospect that failed during the lapsed-session window, and the campaign resumes on its normal schedule, respecting the per-account ramp and per-campaign cap split as usual.

Profile-level: vanity URL changed (sometimes — affects only one prospect at a time)

LinkedIn lets users edit their public profile URL at any time. Your CSV export captured the URL as-of export day; if the owner changed it since, the lookup returns a genuine "profile not found" — the handle no longer exists. This affects exactly one prospect at a time — the others on the campaign continue sending normally.

Fix: open the prospect on LinkedIn, copy the current URL from your browser's address bar, click Edit URL on the row in the Skipped prospects panel, and paste. The prospect re-enrolls within five minutes.

Profile-level: profile is private, restricted, or deleted (rare — affects one prospect)

If the LinkedIn account was closed or the profile was set to private since your CSV export, no lookup is possible. This produces the same per-prospect "profile not found" signal as the vanity-URL change.

Fix: click Exclude on the row in the Skipped prospects panel to remove the prospect from the campaign. The bulk-exclude action is available if multiple rows hit this case.

What you'll see in the Skipped panel

The Skipped panel on the LinkedIn campaign detail page now distinguishes between the two failure shapes so you don't have to guess:

Account-level banner. When WarmySender detects that your LinkedIn session has lapsed, a single calm amber banner appears at the top of the Skipped panel: "Your LinkedIn account needs to be reconnected. Your LinkedIn session lapsed. Reconnect once and any pending actions on this campaign will automatically resume." with a one-click Reconnect button. The per-prospect rows for affected prospects are folded into the banner — you no longer get a 39-chip wall when there's actually one underlying cause.
Per-prospect chips. Rows that failed because the profile genuinely couldn't be found (vanity-URL change or deleted profile) still show their individual chips with Edit URL / Exclude actions, because those genuinely need per-row attention.

The banner suppression is one-way: as soon as you reconnect and the account-level signal clears, any rows that still have a real per-prospect issue reappear as individual chips. You never lose visibility on rows that genuinely need your attention.

How WarmySender keeps your LinkedIn account safe during a session lapse

Per our account-safety invariant — account safety always wins over throughput — a lapsed session is treated as a stop signal, not a retry-faster signal. Two layers protect you:

Per-account safety guard. When WarmySender sees the same LinkedIn account fail to authenticate three times in a row within a sixty-second window, the safety guard trips. While tripped, WarmySender stops calling LinkedIn for that account, marks the account as needing reconnection, and surfaces the in-app banner. Suppressing the calls protects you from cascading failures that would otherwise increase LinkedIn-side scrutiny on the account.
Suppression remains in place until you reconnect. WarmySender does not "test" the session by sending another call every few minutes. Doing so could increase LinkedIn-side scrutiny. Instead, the safety guard holds the line and the in-app banner becomes the actionable signal.

WarmySender classifies the underlying signal precisely so the wrong fix never gets applied. A session lapse is treated as account-level (one reconnect resolves every affected prospect at once). A genuine "profile not found" is treated as per-prospect (Edit URL or Exclude on that one row). A throttling response is treated as a temporary back-off (WarmySender automatically retries later). Only a real "profile not found" lands on the original "Unresolvable URL" per-prospect label.

How WarmySender detects this faster going forward

WarmySender's recurring health check now actively probes the same path that campaigns use at send time, so a silent session lapse shows up in the regular check cycle. The dashboard updates automatically and the in-app banner appears the moment the lapse is detected, instead of waiting until your next campaign send to surface the problem.

What happens after I reconnect

Reconnecting fires a scoped, idempotent recovery. WarmySender:

Looks up every pending or recently-failed action on the reconnected account that the lapsed session interfered with.
Filters to actions whose last attempt happened within the lapsed-session window, so old genuinely-failed rows are not re-attempted.
Re-schedules them at staggered times that respect the campaign's sending window, the per-account daily cap, the per-account ramp ceiling, and the per-recipient cooldown.

You do not need to re-import any CSV, manually click any row, or take any other action. The first re-attempted sends typically begin within five minutes of the reconnect landing; the full backlog drains over the next sending window respecting all caps.

How to verify the reconnect worked

Settings → LinkedIn Accounts. The affected account's pill should be back to "Connected" with a fresh "Last activity" timestamp. If it still shows "Reconnect needed", the reconnect did not complete — try it again.
Campaign detail page. The Skipped panel reconnect banner should disappear within a few minutes once the lapsed-session state clears. Per-prospect chips that genuinely need attention (real profile-not-found cases) remain.
Dashboard activity. Within the campaign's next sending window, you should see new sends landing on the previously-stuck prospects. Acceptance webhooks fire normally as those prospects engage.

Common questions

Why didn't WarmySender automatically reconnect my account when the session lapsed?

Reconnecting requires user-initiated browser interaction — LinkedIn's security model does not let a third-party tool refresh a session that LinkedIn invalidated. Even if it were technically possible, doing so silently would mean you'd never see the signal that LinkedIn's automation-detection systems flagged your session, which is exactly the moment the right answer is "slow down and human-verify," not "retry harder." The in-app banner is the actionable signal and the reconnect itself is a thirty-second flow.

Will my campaign caps reset or my ramp progress reset when I reconnect?

No. The per-account ramp counter, the per-campaign daily cap, and the per-recipient cooldown are all preserved across reconnects. The recovery re-schedules failed jobs at staggered times within the existing caps — never as a burst. If your daily cap is already exhausted by other sending today, the re-attempted sends will land on tomorrow's first valid slot, same as any newly-enrolled prospect.

Are prospects that failed during the lapsed-session window lost or marked permanently failed?

No. Those rows are kept in a re-tryable state and the recovery at reconnect time moves them back to scheduled for the campaign to re-pick up. Only true per-prospect failures (genuine "profile not found" — vanity-URL change, deleted profile) are marked permanently failed, and you can still recover those via Edit URL or Exclude.

Does the safety guard tripping count against any account-safety penalty on LinkedIn's side?

No. The safety guard is a WarmySender-side circuit. It does not call out to LinkedIn while tripped, so it makes no requests and creates no LinkedIn-side signal. Tripping it actually reduces your LinkedIn-side risk surface because it prevents a cascade of additional failing calls.

Why does the banner say "your session has lapsed" instead of just "reconnect"?

Because naming the cause helps. A blanket "Reconnect" with no explanation invites the question "is something genuinely broken on WarmySender's side?" — and the honest answer is no, your LinkedIn session lapsed for one of a small number of well-known reasons. That precision lets you decide whether to investigate the reason (IP change, security challenge, etc.) or just reconnect and move on. Most customers reconnect and move on; the few who want to investigate now have the information.

What if I reconnect and the banner reappears within an hour?

That signals an underlying account-side issue: LinkedIn is re-invalidating the session shortly after each reconnect. Most common causes: (1) a security challenge or "Was this you?" interstitial that you haven't fully cleared in your browser; (2) a region/IP change that LinkedIn keeps treating as suspicious; (3) a recent password change or 2FA reset that left orphan sessions LinkedIn is still cleaning up. Email [email protected] with the LinkedIn account email and the approximate reconnect-then-relapse timing and we'll dig into the upstream signal.

Is this the same as the "Unresolvable URL" case where my Sales Navigator URLs can't be resolved?

No. Sales Navigator URL resolution failure is a one-shot per-prospect issue — the URL is genuinely not resolvable to a public profile and the right fix is per-row (Edit URL or Exclude). This page covers the opposite case — the URL is fine, your session is the problem, and the right fix is one reconnect that recovers every affected prospect in one motion.

Will reconnecting affect my email warmup or other channels?

No. Email warmup runs on a completely separate scheduler, and your email mailboxes remain connected through LinkedIn reconnect events. The reconnect flow is scoped to the single LinkedIn account that needs it — your other LinkedIn accounts, your email campaigns, and your warmup activity are not touched.

What if I see prospects failing without a banner appearing?

We recently improved the detection so that even slow-running campaigns surface this banner within minutes. If you ever see prospects failing one at a time and don't yet see a reconnect prompt, give it a few minutes — if it doesn't appear, contact support and we'll take a look right away. Going forward, the banner should appear automatically whenever your LinkedIn session needs to be refreshed.