proposal agent broke parsing a Word SOW attachment scope hours extracted as zero

TL;DR

Fix this in the SOW attachment parser by acting on the exact message first: open the Word SOW, move the scope hours out of any text box or floating table into a normal table in the document body, reparse, and reject the parse if total scope hours read as zero while the document names an hours table. 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.

proposal agent broke parsing a Word SOW attachment scope hours extracted as zero

Use this when

• The operation in the SOW attachment parser fails with this exact message: proposal agent broke parsing a Word SOW attachment scope hours extracted as zero.
• The same failure repeats on retry with unchanged inputs.
• A proposal, quote or send 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 SOW attachment parser, and copy the full message plus the proposal, quote or account 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: open the Word SOW, move the scope hours out of any text box or floating table into a normal table in the document body, reparse, and reject the parse if total scope hours read as zero while the document names an hours table. Verify: the reparsed scope hours match the hours table in the SOW and the zero hours guard passes.
3. Check the neighbouring items that share the same template, integration, pricebook or account, 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 against the source system in the SOW attachment parser so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the SOW attachment 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 read only the document body flow, so hours held in floating elements were never reached and extracted as zero.

Variant phrasings

proposal agent broke parsing a Word SOW attachment scope hours extracted as zero

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: proposal agent broke parsing a Word SOW attachment scope hours extracted as zero

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

Troubleshooting this failure in the SOW attachment parser

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 SOW attachment parser at current versions, plus the platform API or console 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/pstFdcPA55Tvqry96JYkjz_Q

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

Thread query: proposal agent broke parsing a Word SOW attachment scope hours extracted as zero

TL;DR: Fix this in the SOW attachment parser by acting on the exact message first: open the Word SOW, move the scope hours out of any text box or floating table into a normal table in the document body, reparse, and reject the parse if total scope hours read as zero while the document names an hours table. 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.