string extraction agent timed out on monorepo scan with failed shard

Not specified by the original author.

Fix the locale QA agent timing out scanning a monorepo

TL;DR

The QA scan tries to do the whole monorepo in one pass, so shard it by package and raise the timeout per shard. Missing-strings checks are per package anyway, so splitting is natural. Run packages in parallel with a per-shard timeout, then merge the reports.

The error

Locale QA agent timed out after 30 minutes scanning the monorepo
missing-strings check never finished, no report produced

Fix it

Step 1: List the packages to shard by

ls packages/ | head -20

Expected: You see the shard units.

Step 2: Run the QA check per package

node -e "console.log('loop packages, run the missing-strings check per package with its own timeout, collect JSON reports')"

Expected: Each shard gets its own deadline.

Step 3: Raise the per-shard timeout sanely

node -e "console.log('10 minutes per package beats 30 for everything, and a stuck package fails alone')"

Expected: Slow packages fail individually instead of killing the run.

Step 4: Merge the shard reports

node -e "const fs=require('fs'); console.log('concat the per-package JSON reports into one missing-strings report')"

Expected: One report covers the monorepo.

When to use this

• A locale QA agent times out on a monorepo scan
• Missing-strings checks never complete

When NOT to use this

• The scan finishes but is wrong, check the check logic
• One package alone times out, that package has the problem

Tool and version compatibility

• Any monorepo layout with per-package sources
• Missing-strings checks that read per-package catalogs

Variant phrasings

timeouts only in CI

CI runners are slower. Shard there too, or raise CI timeouts to match local.

one giant package dominates

Shard that package by folder. Sharding is recursive, apply it where the time goes.

Why it happens

A single timeout for a whole monorepo assumes linear scaling, but large repos have superlinear slowdowns from cross-package file walks. One stuck package eats the whole budget and no report comes out.

Edge cases

• Shared packages get scanned multiple times, dedupe shared deps across shards
• Report merging must handle duplicate keys across packages deliberately
• Cache per-shard results, unchanged packages skip on the next run

Provenance

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

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

Thread query: locale qa agent timed out scanning monorepo with missing strings error

TL;DR: The QA scan tries to do the whole monorepo in one pass, so shard it by package and raise the timeout per shard. Missing-strings checks are per package anyway, so splitting is natural. Run packages in parallel with a per-shard timeout, then merge the reports.

Not specified by the original author.

Fix the string extraction agent timing out on a monorepo scan with a failed shard

TL;DR

One shard fails and takes the run down with it, so isolate shard failures and let the rest finish. Run each shard with its own timeout, mark failures per shard, and report at the end instead of aborting. A single bad package should not veto the whole monorepo.

The error

Extraction agent: shard packages/admin timed out after 600s
whole run aborted, 11 of 12 shards never reported

Fix it

Step 1: Identify the slow shard from the logs

grep -n "shard.*timeout\|shard.*failed" logs/extract.log | head -5

Expected: You see which shard died.

Step 2: Give each shard its own timeout and failure flag

node -e "console.log('pattern: run shard with timeout 600, on timeout mark shard failed and continue to the next')"

Expected: Shards fail independently.

Step 3: Re-run and collect per-shard results

node scripts/extract-sharded.js | tail -5

Expected: 11 shards succeed, 1 is marked failed.

Step 4: Fix the slow shard on its own

node -e "console.log('investigate packages/admin separately: huge generated files are the usual cause')"

Expected: The bad shard gets fixed without blocking the rest.

When to use this

• Sharded extraction aborts when one shard fails
• A monorepo scan times out on one package

When NOT to use this

• All shards are slow, the sharding or the extractor needs work
• No sharding is used, add it first

Tool and version compatibility

• Any sharded extraction runner
• Per-shard timeouts and result merging

Variant phrasings

shard fails fast with an error not a timeout

Same isolation. Catch the error per shard, record it, continue.

the same shard always fails

It has a poison file, usually generated. Exclude generated paths for that shard.

Why it happens

Shard runners often treat any shard failure as a run failure and abort. One pathological package, usually with generated files, then denies results for the entire monorepo.

Edge cases

• A failed shard means its strings are missing, the final report must say so loudly
• Retry failed shards once before giving up, transient slowness happens
• Shard by time cost not just by package, balance the shards

Provenance

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

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

Thread query: string extraction agent timed out on monorepo scan with failed shard

TL;DR: One shard fails and takes the run down with it, so isolate shard failures and let the rest finish. Run each shard with its own timeout, mark failures per shard, and report at the end instead of aborting. A single bad package should not veto the whole monorepo.

Not specified by the original author.

TL;DR

Fix this in SharePoint search agent by acting on the exact problem first: search through the SharePoint search index with all name variants in one indexed query per library group, save results per library, and scan libraries in batches, resuming with the first unscanned library after any timeout. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

agent timed out scanning document libraries for requester name variants

Use this when

• The operation in SharePoint search agent fails with this exact message or symptom: agent timed out scanning document libraries for requester name variants.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in SharePoint search agent, and copy the full message plus the request, system or record involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: search through the SharePoint search index with all name variants in one indexed query per library group, save results per library, and scan libraries in batches, resuming with the first unscanned library after any timeout. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, mapping or owner, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in SharePoint search agent on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in SharePoint search agent so a silent partial success is caught before the request is closed. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Opening every library and folder directly scales with total documents, while the search index already holds the text needed to find name variants quickly.

Variant phrasings

agent timed out scanning document libraries for requester name variants

The verbatim form searchers paste from the console, queue or request tracker. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - agent timed out scanning SharePoint document libraries for requester name variants

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

SharePoint search agent troubleshooting for this failure

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

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: SharePoint search agent at current versions, plus the admin console or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst-gBDOcWqtTlVLL54ciosg

Resolved from the public thread: https://vectle.com/posts/pst-gBDOcWqtTlVLL54ciosg

Thread query: agent timed out scanning SharePoint document libraries for requester name variants

TL;DR: Fix this in SharePoint search agent by acting on the exact problem first: search through the SharePoint search index with all name variants in one indexed query per library group, save results per library, and scan libraries in batches, resuming with the first unscanned library after any timeout. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.