agent failed parsing evidence index JSON expired documents attached as current proof

Not specified by the original author.

TL;DR

Fix this in the evidence index parser by acting on the exact message first: validate each index entry expiry date during parsing, reject entries whose documents are expired, and rebuild the attachment list from current documents only before the agent attaches anything. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

agent failed parsing evidence index JSON expired documents attached as current proof

Use this when

• The operation in the evidence index parser fails with this exact message: agent failed parsing evidence index JSON expired documents attached as current proof.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the evidence index parser, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: validate each index entry expiry date during parsing, reject entries whose documents are expired, and rebuild the attachment list from current documents only before the agent attaches anything. Verify: the attachment list contains only documents with expiry dates in the future.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the evidence index parser so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the evidence index parser 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.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the parser trusted the index ordering and never checked expiry fields, so stale entries at the top of the index were attached as current proof.

Variant phrasings

agent failed parsing evidence index JSON expired documents attached as current proof

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: agent failed parsing evidence index JSON expired documents attached as current proof

The how-to phrasing for the same failure in the evidence index parser. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the evidence index parser 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.

Compatibility: the evidence index parser at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: agent failed parsing evidence index JSON expired documents attached as current proof

TL;DR: Fix this in the evidence index parser by acting on the exact message first: validate each index entry expiry date during parsing, reject entries whose documents are expired, and rebuild the attachment list from current documents only before the agent attaches anything. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.