agent summarized a week of backup reports from email subjects only and missed failures buried in attachments

TL;DR

Subjects are headlines, not reports: the agent summarised from subject lines and missed every failure that lived in the body or the attachment. Parse the full message and its report attachment, extract per-job outcomes from the structured content, and treat any report whose body cannot be parsed as an alert in itself rather than a quiet pass. Email-borne reports should be replaced by API or file feeds where the platform offers them.

agent summarized a week of backup reports from email subjects only and missed failures buried in attachments

Use this when

• The job or restore fails with this symptom: agent summarized a week of backup reports from email subjects only and missed failures buried in attachments.
• You are working on an agent summarising emailed backup reports and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A vendor whose only report channel is email, where the fix is full parsing of that email including attachments, plus a parser-failure alert.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Collect the week's report emails and extract outcomes from bodies and attachments with a real parser. Verify: the true outcome set is recovered
2. Diff the recovered outcomes against the agent's subject-based summary and list every missed failure. Verify: the under-reporting is enumerated
3. Rewrite ingestion to parse attachments in their native format, CSV, HTML, or PDF tables, into per-job records. Verify: ingestion reads the actual report
4. Add a rule that an unparseable report raises an ingestion alert instead of contributing a silent success. Verify: parse failures are loud
5. Re-issue the week's summary corrected, and notify the report's consumers of the earlier gap. Verify: the record is corrected transparently

Variant phrasings

agent summarized backup reports email subjects only missed failures attachments

The verbatim phrasing.

agent email report ingestion parse body attachment per job fix

The ingestion phrasing.

backup report summary wrong subjects headlines agent attachment truth

The headline phrasing.

Compatibility: Agent summarisation of backup reports delivered by email

Why it happens

Email subjects are written to be scanned by humans who then open the message; the failure detail lives one level down by design. An agent that stops at the subject inherits the headline's optimism, and attachments, where vendors put the machine-readable truth, might as well not exist.

Edge cases / pitfalls

• Subject conventions differ per vendor and drift over time; even subject parsing is a fragile primary source.
• Where reports arrive as PDFs, table extraction needs validation sampling against known job outcomes.

Provenance

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

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

Thread query: agent summarized a week of backup reports from email subjects only and missed failures buried in attachments

TL;DR: Subjects are headlines, not reports: the agent summarised from subject lines and missed every failure that lived in the body or the attachment. Parse the full message and its report attachment, extract per-job outcomes from the structured content, and treat any report whose body cannot be parsed as an alert in itself rather than a quiet pass. Email-borne reports should be replaced by API or file feeds where the platform offers them.