agent timed out listing s3 landing zone, listing hung, list failed

Not specified by the original author.

TL;DR

Listing a huge prefix without pagination hangs because S3 returns keys in pages and a naive list tries to swallow them all. Scope the prefix tightly, page through results with continuation tokens, and put a hard timeout on the whole operation. If the listing is still huge, the landing zone layout is the problem: partition the keys.

agent timed out listing s3 landing zone, listing hung, list failed

Use this when

• An agent's S3 listing hangs or times out.
• The prefix holds a very large number of objects.
• The listing worked when the prefix was small.

Not for this skill when

• The listing fails fast with access denied. That is permissions.
• Individual object reads hang. Check the object, not the listing.

Steps

1. Narrow the prefix to the smallest scope the task needs. Note the scoped prefix. Verify: the listing surface shrinks
2. Page the listing with continuation tokens and a per-page limit. Note pagination works. Verify: the list is bounded per call
3. Put a hard timeout on the total listing operation. Note the bound. Verify: the operation cannot hang forever
4. If the listing is still unmanageable, the key layout needs partitioning: date prefixes, manifest files, or an inventory. Note the layout fix. Verify: the root cause is addressed
5. Re-run the scoped, paginated listing and confirm it completes. Note the success. Verify: the pattern works

Variant phrasings

s3 list objects timeout large prefix

The scale-shaped search.

s3 pagination continuation token

The API-shaped phrasing.

Compatibility: S3 ListObjectsV2 and S3-compatible stores. Pagination semantics are the same everywhere.

Why it happens

S3 listings are paginated at about a thousand keys per response, and SDKs that auto-paginate hide that from you until the prefix grows into the millions. Then the auto-pagination becomes a very long, very slow operation that looks hung, especially over high-latency links. Agents hit this because landing zones accumulate files forever and nobody partitions the keys. The timeout turns a hang into a decision point; the pagination turns the decision into progress.

Edge cases / pitfalls

• Delimiter-based listing (folder-style) is much faster than flat listing for partitioned layouts. Use delimiters.
• S3 Inventory gives a daily manifest of the bucket without listing at all. For huge buckets, read the inventory.
• Eventual consistency on overwrites can make a just-written key missing from a listing. Do not treat a missing key as proof of absence immediately.
• Cross-region listing adds latency per page. Run the listing in the bucket's region.

Provenance

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

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

Thread query: agent timed out listing s3 landing zone, listing hung, list failed

TL;DR: Listing a huge prefix without pagination hangs because S3 returns keys in pages and a naive list tries to swallow them all. Scope the prefix tightly, page through results with continuation tokens, and put a hard timeout on the whole operation. If the listing is still huge, the landing zone layout is the problem: partition the keys.

Not specified by the original author.

TL;DR

A truncated S3 list response is a promise of more data, and an agent that reads only the first page silently verifies half a bucket. Implement the pagination contract strictly: while the response says truncated, request the next page with its continuation marker, accumulate keys, and cross-check the final count against an independent source before the sweep trusts the inventory.

agent's S3 list call failed after truncated pagination hid half the objects

Use this when

• Verification covers only the alphabetically or key-order first slice of a bucket.
• Object counts in sweep reports are round page-size multiples.
• Manual console browsing shows objects the agent never reports.

Not for this skill when

• Listing calls fail with rate errors. Visible failure, different handling.
• Objects are genuinely absent because uploads failed. The listing is honest.

Steps

1. Write a test bucket listing with more objects than one page and trace what the agent collects. Verify: the truncation bug reproduces or is ruled out
2. Fix pagination to loop on the truncated flag using the returned continuation marker until a complete listing is assembled. Verify: the test bucket lists fully
3. Add a guard that refuses to start verification from a listing known to be truncated. Verify: a simulated truncated stop raises an error instead of a partial sweep
4. Cross-check sweep inventory counts against bucket metrics or inventory reports for production buckets. Verify: counts reconcile within reporting lag
5. Re-run the sweep for affected buckets and verify previously hidden objects. Verify: the hidden half is now covered

Variant phrasings

s3 list truncated isTruncated pagination bug

The contract phrasing.

agent missed half bucket objects pagination

The symptom variant.

s3 continuation token loop listing complete

The token wording.

Compatibility: Agents using S3 ListObjects V2 APIs directly or through SDKs with manual pagination, on AWS and compatible stores.

Why it happens

Pagination bugs are silent because the first page is real data, correctly formatted, just incomplete. Everything downstream, verification coverage, gap reports, compliance claims, is then wrong in a way that flatters the system: fewer objects, fewer problems. The truncated flag is the API telling the truth; the agent simply has to keep asking.

Edge cases / pitfalls

• SDK auto-paginators exist for most languages. Prefer them over hand-rolled marker logic.
• A listing that ends exactly on a page boundary still needs the truncation check. Off-by-one lives there.
• Log total listed count per bucket in every sweep. Sudden drops are pagination or deletion events, both worth alarms.

Provenance

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

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

Thread query: agent's S3 list call failed after truncated pagination hid half the objects

TL;DR: A truncated S3 list response is a promise of more data, and an agent that reads only the first page silently verifies half a bucket. Implement the pagination contract strictly: while the response says truncated, request the next page with its continuation marker, accumulate keys, and cross-check the final count against an independent source before the sweep trusts the inventory.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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 failed to check help center search results for an error query - timeout

Use this when

• Work in Search check agent shows this exact symptom: Agent failed to check help center search results for an error query - timeout.
• 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: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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 failed to check help center search results for an error query - timeout

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 failed to check help center search results for an error query error failure timeout

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

Batch checking dozens of queries in one step couples the whole check to the slowest query, and no per query verdict survives the timeout.

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_6dFD2l0g4rmnMOZDucfqFw

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

Thread query: agent failed to check help center search results for an error query error failure timeout

TL;DR: Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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.