agent's email parser failed to read the backup report and called it a success

TL;DR

Emailed backup reports trap naive parsers because subject lines say the job name, summaries bury the failed objects, and footers contain the word success in boilerplate. Parse the structured result fields in the body or the attached report, extract per-object outcomes, and classify the report by its worst object result, never by keyword presence.

agent's email parser failed to read the backup report and called it a success

Use this when

• Agent marks emailed reports success while the body lists failed VMs or files.
• Boilerplate words like successful in disclaimers trigger false success.
• Reports in HTML are misread while plain text versions parse correctly, or the reverse.

Not for this skill when

• Reports are never delivered to the mailbox the agent reads. Delivery routing problem.
• The agent parses product logs directly with record issues. Different input channel.

Steps

1. Collect real report emails across outcomes: success, warning, failure and partial. Verify: a labelled sample set exists
2. Identify the authoritative result fields in body or attachment and document where per-object outcomes live. Verify: the field map is written from samples
3. Rewrite classification to use those fields and take the worst per-object outcome as the report outcome. Verify: the sample set classifies perfectly
4. Strip boilerplate and signatures before any keyword fallback is applied, and remove keyword-only classification entirely for structured reports. Verify: footer text cannot flip a result in tests
5. Run the parser over the last month of reports and reconcile with the backup console. Verify: classifications match the console record

Variant phrasings

email report parser false success backup agent

The false-success phrasing.

agent misread backup report body warnings

The body variant.

parse emailed backup report per object result

The structure wording.

Compatibility: Agents reading Veeam, Acronis and similar emailed reports in HTML and plain text, plus CSV, XML and PDF attachments.

Why it happens

Email reports are designed for a human skimming with judgement, so the decisive facts are visual and positional rather than labelled. Keyword parsers fail predictably on them because natural language reports mention success and failure in the same message whenever outcomes are mixed. Structural field parsing with worst-outcome classification reproduces the human judgement the report assumed.

Edge cases / pitfalls

• If the product can send structured formats or API webhooks instead, migrate the agent. Email is the worst integration surface.
• HTML parsing must handle the actual template your product version sends. Templates change between versions.
• Keep the raw email linked from every classification so a human can overrule the parser quickly.

Provenance

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