screenshot agent timed out snapshotting locale pages in playwright run failed

Not specified by the original author.

Fix the screenshot agent timing out snapshotting locale pages in Playwright

TL;DR

Snapshotting every locale page serially exceeds the timeout, so parallelize with a worker pool and raise per-page timeouts. Locale suites multiply pages by languages, and serial runs time out. Shard pages across workers, snapshot in parallel, and collect the results.

The error

Screenshot agent: timed out snapshotting 200 locale pages
Playwright run failed after 30 minutes, 40 pages captured

Fix it

Step 1: Count the page-locale combinations

node -e "console.log('pages times locales = total snapshots, check the number')"

Expected: You see the scale that serial runs cannot meet.

Step 2: Shard across workers

node -e "console.log('pattern: split the URL list across 4 workers, each with its own browser context')"

Expected: Snapshots parallelize.

Step 3: Raise the per-page timeout sanely

node -e "console.log('60s per page with 4 workers beats one 30-minute global timeout')"

Expected: Slow pages fail alone instead of killing the run.

Step 4: Re-run and confirm full coverage

node scripts/locale-shots.js | tail -3

Expected: All 200 pages captured.

When to use this

• A screenshot agent times out on large locale page sets
• Playwright runs die partway through snapshots

When NOT to use this

• One page always times out, debug that page
• Screenshots are wrong, check the rendering

Tool and version compatibility

• Playwright worker pools, sharded snapshot runs
• Per-page timeouts

Variant phrasings

workers exhaust memory

Fewer workers with more RAM each, or restart contexts between shards.

CI is slower than local

Size the pool for CI, not your laptop. Detect CI and shrink the pool.

Why it happens

Snapshot count multiplies pages by locales, and serial execution scales linearly past any reasonable timeout. One global deadline for hundreds of page loads guarantees a timeout, while sharding keeps each unit under its own budget.

Edge cases

• Dedupe identical pages across locales before snapshotting
• Stagger worker starts so they do not hammer the server at once
• Save progress per page so reruns skip completed snapshots

Provenance

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

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

Thread query: screenshot agent timed out snapshotting locale pages in playwright run failed

TL;DR: Snapshotting every locale page serially exceeds the timeout, so parallelize with a worker pool and raise per-page timeouts. Locale suites multiply pages by languages, and serial runs time out. Shard pages across workers, snapshot in parallel, and collect the results.

Not specified by the original author.

screenshot agent timed out on infinite scroll locale pages

TL;DR

Fixes the screenshot agent timing out on infinite-scroll pages in locale QA. Scroll to a fixed depth or stub the feed before capturing. Use when locale screenshots time out on feeds. Not for static pages.

The error

Screenshot agent timed out after 120s scrolling the localized activity feed.

Fix it

Step 1: Confirm the infinite scroll

node -e "console.log('the feed loads more items on every scroll; the agent never reaches the bottom')"

Expected: You confirm the page never settles.

Step 2: Cap the scroll depth

node -e "console.log('scroll a fixed number of viewports, then capture')"

Expected: The agent captures a bounded page.

Step 3: Re-run the locale suite

node -e "console.log('confirm screenshots complete for every locale')"

Expected: The suite finishes.

When to use this

• Screenshot capture times out on feed pages
• The page loads content forever on scroll

When NOT to use this

• Static pages time out, check the page load
• Screenshots capture but look wrong, check the rendering

Tool and version compatibility

• Playwright and Puppeteer
• Any infinite-scroll feed

Variant phrasings

timeout only in some locales

Those locales have more content. The cap must be content-independent.

screenshots differ run to run

Stub the feed data so captures are deterministic.

Why it happens

Infinite scroll never reaches a settled state, so an agent waiting for network idle or page bottom waits forever. Bounding the scroll gives the agent a finish line.

Edge cases

• Lazy-loaded images need a settle wait after the scroll cap
• Virtualized lists render only the viewport; capture scrolled positions separately
• Locale changes the item count, so depth must not depend on content

Provenance

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

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

Thread query: screenshot agent timed out on infinite scroll locale pages

TL;DR: Fixes the screenshot agent timing out on infinite-scroll pages in locale QA. Scroll to a fixed depth or stub the feed before capturing. Use when locale screenshots time out on feeds. Not for static pages.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: rank the query list by impressions and check in that order with a per query time budget, publish the partial verdict table at the budget end, and schedule the tail queries for the next run instead of extending this one. 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.

Agent timed out checking help center search results - slow run

Use this when

• Work in Search check agent shows this exact symptom: Agent timed out checking help center search results - slow run.
• 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: rank the query list by impressions and check in that order with a per query time budget, publish the partial verdict table at the budget end, and schedule the tail queries for the next run instead of extending this one. 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

Agent timed out checking help center search results - slow run

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 - agent timed out when agent tried to check help center search results for an error query error timeout failure slow

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

Checking in log order spends equal time on queries nobody searches, and the timeout then hides the verdicts for the queries that matter most.

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_u5H38S3gFWnDXMhPsVGA2Q

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

Thread query: agent timed out when agent tried to check help center search results for an error query error timeout failure slow

TL;DR: Fix this in Search check agent by acting on the exact symptom first: rank the query list by impressions and check in that order with a per query time budget, publish the partial verdict table at the budget end, and schedule the tail queries for the next run instead of extending this one. 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.