linkedin CHALLENGE_REQUIRED on agent login - the verify-it's-you checkpoint with no solver path

TL;DR

A LinkedIn checkpoint is a stop sign, not a puzzle to solve. Do not attempt to bypass or automate the verify-it's-you screen. Halt the session, log the checkpoint, alert a human to clear it manually, and keep the agent parked until the session is healthy again.

linkedin CHALLENGE_REQUIRED on agent login  -  the verify-it's-you checkpoint with no solver path

Steps

1. Stop the automation the moment CHALLENGE_REQUIRED appears. Do not click through, refresh-loop, or retry the login. Expected: no further login attempts go out.

2. Log the checkpoint with a timestamp, the account, and what the agent was doing when it hit. This is the incident record. Expected: the operator can see exactly when and where the session died.

3. Alert a human operator to clear the checkpoint manually in a real browser. Only the account owner clears it. Expected: a human acknowledges and takes over the session.

4. While parked, queue the agent's pending work (messages, connection steps, profile reads) with their original order preserved. Nothing is dropped, nothing is sent half-done. Expected: the backlog waits intact for a healthy session.

5. Before resuming, verify the session is clean (a simple profile read succeeds with no challenge), then restart the queue at a calm pace. Add a session-health check that parks the agent automatically on the next challenge. Expected: the agent resumes without triggering a second checkpoint.

Use this when

• The agent hits CHALLENGE_REQUIRED or any verify-it's-you screen on LinkedIn.
• A session that worked yesterday now demands verification.
• Login attempts start failing in a way that smells like bot detection.

Not for this skill when

• The failure is wrong credentials (a login error, not a challenge).
• The block is a rate limit with a clear retry window.
• The task is API-based and never touches the login flow.

Variant phrasings

• "linkedin checkpoint challenge agent stuck"
• "CHALLENGE_REQUIRED verify it's you linkedin automation"
• "linkedin session flagged checkpoint what to do"

Why it happens

LinkedIn challenges sessions that look automated: datacenter IPs, headless browsers, inhuman timing. The checkpoint exists to confirm a human is behind the account. There is no legitimate solver path for an agent, and attempting one (captcha farms, challenge bypasses) risks a permanent restriction. The correct engineering response is to stop and hand off.

Edge cases

• Repeated checkpoints on the same account mean the automation pattern itself is the problem. Slow down, use residential session patterns, or move the work to approved APIs.
• Never let the agent "wait and retry" the login on a timer. Retry loops escalate a checkpoint into a restriction.
• If checkpoints follow a human clearing it and immediate re-automation, the session needs a cool-down period before the agent resumes.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AKcctHJlDldvoNXnqJvXjQ