## TL;DR
Fix this in the clause agent workflow by acting on the exact problem first: open the scanned amendment the parser failed on, check its scan quality and page orientation, rerun it through OCR with deskew and higher resolution, feed the cleaned text into the step that will update the clause library after a policy change, and confirm the parsed clauses are extracted. Do not rerun the same workflow unchanged, because the same inputs produce the same failure. Prove the fix on one workflow run first, then rerun the full scope and reconcile the results.

```text
parser failed on scanned amendment for update the clause library after a policy change error parsing failure
```

## Use this when
- The agent workflow fails with this exact problem: parser failed on scanned amendment for update the clause library after a policy change error parsing failure.
- The same failure repeats on retry with unchanged inputs.
- A clause search, drafting, review or reporting task run by the agent is blocked until this is resolved.

## Not for this skill when
- The notice is a platform outage from the vendor or the clause bank provider. Resolve that first, then return here if this problem remains.
- The operation completes and you only disagree with a clause wording or negotiation position. That is a legal owner decision, not this failure.

## Steps
1. Reproduce the failure on one named run of the task to update the clause library after a policy change and record the full problem text plus the contract or clause set involved. Verify: the failure is reproduced on demand on a named run, not only seen in a log.
2. Apply the specific fix for this problem: open the scanned amendment the parser failed on, check its scan quality and page orientation, rerun it through OCR with deskew and higher resolution, feed the cleaned text into the step that will update the clause library after a policy change, and confirm the parsed clauses are extracted. Verify: the single failing workflow run now behaves as the fix predicts, or the corrected output is visible on the run.
3. Check neighbouring steps in the same workflow that share the same clause bank connection, playbook or session, because this class of failure rarely affects only one step. Verify: the neighbouring steps are listed and each is marked affected or clear.
4. Rerun the original task in the workflow on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the task completes and the original problem does not appear.
5. Compare the result against the source of truth, the clause bank record, the playbook position or the source document, 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 workflow run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Variant phrasings

### parser failed on scanned amendment for update the clause library after a policy change error parsing failure
The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single workflow run proof, then the full rerun.

### How to fix - parser failed on scanned amendment for update the clause library after a policy change error parsing failure
The how to phrasing for the same failure in the clause agent workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### The clause agent workflow 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
The parser expects machine readable text, and a scanned amendment with skewed, low contrast or handwritten pages yields no usable text layer, so the parse step returns an error instead of clause content.

## Edge cases
- The clause bank, playbook or source document changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
- The single workflow run proof passes but the full rerun still fails on other contracts. Treat each remaining failure as its own scope, because a shared connection, playbook or session can hide more than one cause.
- The source systems disagree on the correct value. The clause bank governs approved wording, the playbook governs negotiation position, and the source document governs extracted facts; record which source won and why.

Compatibility: Clause library and agent workflow tooling at current versions, plus the clause bank, playbook or document source 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_5jnftXBFlCHgYtACDhDZKw