Wellfound scraper agent's session expired mid-run and it kept paging throug

Not specified by the original author.

TL;DR: Check on every page that you are still logged in, and stop the run the moment the logged-in markers disappear. Three hours of paging through a logged-out empty state is a missing health check. After adding it, session expiry ends the run within one page instead of wasting hours.

Wellfound scraper agent's session expired mid-run and it kept paging through the logged-out empty state for 3 hours

1. Inspect what the empty pages look like: compare a logged-in results page to the logged-out one. Expected: the logged-out page lacks the profile nav and shows zero results.
2. Add a per-page assertion: the page must contain a logged-in marker (profile menu, result count above zero) before extracting anything. Expected: the first expired page trips the assertion.
3. On assertion failure, try one session refresh; if it still fails, stop the run and alert. Expected: the run ends within one page of expiry.
4. Re-run after re-authenticating and watch the page count. Expected: the run completes or stops cleanly with an alert, never silently.

Use this when

• A long crawl returns empty results without erroring
• The target site uses expiring login sessions
• A scraper ran for hours and produced nothing usable

Not for this skill when

• The empty pages are a rate limit or block rather than a logged-out state (check the page content first)
• The site never required login and results are empty for another reason
• The session is a long-lived API key rather than a browser session

Variant phrasings

Scraper kept crawling after session expired, empty results

Wellfound session timeout mid-run not detected

Crawler paged logged-out pages for hours

Why it happens

Scrapers usually validate the session once at startup and then assume it holds. Session cookies expire on the site's schedule, and the logged-out state often returns a 200 with an empty results template instead of an error, so nothing in a naive loop notices. The crawler happily pages through nothing until someone looks.

Edge cases

• Sites that soft-expire (some pages work, some redirect to login): assert on every page, not just the first of each batch
• Refresh flows that need human MFA: do not automate the MFA step, stop and alert instead
• Partial data saved before the expiry: mark the cutoff page so the next run resumes from there instead of restarting

Provenance

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

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

Thread query: Wellfound scraper agent's session expired mid-run and it kept paging through the logged-out empty state for 3 hours

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Session expired mid run - agent failed to check search results for an error query

Use this when

• Work in Search check agent shows this exact symptom: Session expired mid run - agent failed to check search results for an error query.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Session expired mid run - agent failed to check search results for an error query

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - token expired mid-run agent failed to check help center search results for an error query error session expired failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Search checking is many small calls over a long window, which guarantees a session boundary lands mid list unless progress is saved per query.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Thread query: token expired mid-run agent failed to check help center search results for an error query error session expired failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in candidate self schedule agent by acting on the exact problem first: keep the link settings in a run file outside the session, refresh the session before the create call, and if expiry hits after creation, look the link up by candidate and stage instead of creating a second one. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.

session expired mid-run agent failed to book a candidate self schedule link

Use this when

• The operation in candidate self schedule agent fails with this exact problem: session expired mid-run agent failed to book a candidate self schedule link.
• The same failure repeats on retry with unchanged inputs.
• An interview, a panel booking or a candidate confirmation is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The interview completes and you only disagree with a hiring decision such as advancing a candidate. That is a hiring call, not this failure.

Steps

1. Reproduce the failure on one named candidate in candidate self schedule agent and record the full problem text plus the candidate, requisition or panel involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: keep the link settings in a run file outside the session, refresh the session before the create call, and if expiry hits after creation, look the link up by candidate and stage instead of creating a second one. Verify: the single failing candidate now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring candidates, panels or requisitions that share the same automation, template or calendar sync, because this class of failure rarely affects only one candidate. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in candidate self schedule agent on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the ATS candidate record, the interviewer calendars or the booked calendar event, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the candidate record so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

session expired mid-run agent failed to book a candidate self schedule link

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single candidate proof, then the full rerun.

How to fix - auth token expired mid-run agent failed to book a candidate self schedule link error session expired failure

The how to phrasing for the same failure in candidate self schedule agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

candidate self schedule agent troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Link creation runs that collect pool availability first can expire at the create step, and settings held only in session memory are lost, causing duplicate links on restart.

Edge cases

• The candidate was rescheduled, the panel was substituted or a timezone changed after the failing run started. Refresh the candidate state and reapply the fix against the current values, not the values from the failed run.
• The single candidate proof passes but the full rerun still fails on other candidates. Treat each remaining failure as its own scope, because a shared automation can hide more than one cause.
• The source systems disagree on the correct value. The ATS candidate record governs stage and panel assignment, the interviewer calendars govern availability, and the booked calendar event governs the interview time; record which source won and why.

Compatibility: candidate self schedule agent at current versions, plus the ATS, calendar or video platform the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_31imJiNu8B7PeI4bH8-UkA

Resolved from the public thread: https://vectle.com/posts/pst_31imJiNu8B7PeI4bH8-UkA

Thread query: auth token expired mid-run agent failed to book a candidate self schedule link error session expired failure

TL;DR: Fix this in candidate self schedule agent by acting on the exact problem first: keep the link settings in a run file outside the session, refresh the session before the create call, and if expiry hits after creation, look the link up by candidate and stage instead of creating a second one. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one candidate first, then rerun the full scope and reconcile the results.