agent parsed Commvault job status "completed with one or more errors" as full success in the weekly report

Not specified by the original author.

TL;DR

Completed with one or more errors is a distinct status that must surface in reports as partial, not success: the agent's parser collapsed it into the success bucket. Enumerate Commvault's job status values, map this one to a partial or attention category that names the failed components, and re-issue the affected weekly reports with the items that had errors listed individually.

agent parsed Commvault job status "completed with one or more errors" as full success in the weekly report

Use this when

• The job or restore fails with this symptom: agent parsed Commvault job status completed with one or more errors as full success in the weekly report.
• You are working on an agent producing backup status reports from Commvault job data 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 job whose errors are genuinely benign warnings documented by policy, where the fix is an explicit benign-error list, not blanket success.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Collect the distinct status strings the agent consumed in the period and its mapping for each. Verify: the current mapping is exposed
2. Add the errors-present status as its own reported category with the failed items attached from the job detail. Verify: partial outcomes become visible
3. Re-run the report for the current week and diff it against the issued one. Verify: the understatement is quantified
4. Publish a correction for any week where the misclassification hid a real failure. Verify: stakeholders get the corrected picture

Variant phrasings

agent parsed completed with one or more errors as success commvault

The verbatim phrasing.

commvault job status partial errors weekly report agent fix

The partial phrasing.

agent backup report hid job errors status mapping

The mapping phrasing.

Compatibility: Agent parsing of Commvault job status summaries for reports

Why it happens

Status taxonomies encode exactly the distinctions reports exist to convey, and completed with errors is the taxonomy's way of saying look closer. A parser that maps by prefix or by the word completed throws that distinction away, and every consumer of the report inherits the false comfort.

Edge cases / pitfalls

• Fetch the job's error items, not just the status; a partial with a named failed VM is actionable, a count is not.
• Keep the status map in one shared configuration so dashboards and reports cannot drift into different truths.

Provenance

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

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

Thread query: agent parsed Commvault job status "completed with one or more errors" as full success in the weekly report

TL;DR: Completed with one or more errors is a distinct status that must surface in reports as partial, not success: the agent's parser collapsed it into the success bucket. Enumerate Commvault's job status values, map this one to a partial or attention category that names the failed components, and re-issue the affected weekly reports with the items that had errors listed individually.