agent couldn't parse the usage CSV export, run failed

Not specified by the original author.

TL;DR

Inspect the actual bytes: encoding, delimiter, and header row. Then parse with the detected settings, validate headers against expectations, and fail loudly on unexpected shapes instead of producing wrong numbers.

agent couldn't parse the usage CSV export, run failed

Use this when

• A usage CSV export fails to parse in the agent's code.
• The parser assumed comma and UTF-8.
• The vendor recently changed the export.

Not for this skill when

• The export is empty. That is a data problem.
• The export is truncated. Fix the export first.
• The parse succeeds but counts are wrong. Validate the logic, not the parse.

Steps

1. Dump the first bytes of the file and detect the encoding. Verify: you know the real encoding.
2. Identify the actual delimiter; it is not always a comma. Verify: the delimiter is confirmed.
3. Parse with the detected encoding and delimiter. Verify: the parse completes.
4. Validate the headers match expectations. Verify: every expected column exists.
5. Check row counts for sanity. Verify: the totals are plausible.

Variant phrasings

CSV parse failed

The short phrasing.

usage export unreadable

The symptom-first search.

encoding error CSV

The cause-first phrasing.

Compatibility: Any usage CSV export parsed by agent code.

Why it happens

Vendors change encodings and delimiters without notice, and parsers that assume comma plus UTF-8 break. The failure is in the assumption, not the data.

Edge cases / pitfalls

• Semicolon delimiters in European locales; detect, do not assume.
• Header rows that shift position or wording between exports; validate, do not index blindly.
• The file being fine but the agent reading it with the wrong mode; check binary versus text handling.
• Failing loudly matters: a parser that guesses wrong silently is worse than one that errors.

Provenance

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

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

Thread query: agent couldn't parse the usage CSV export, run failed

TL;DR: Inspect the actual bytes: encoding, delimiter, and header row. Then parse with the detected settings, validate headers against expectations, and fail loudly on unexpected shapes instead of producing wrong numbers.

Not specified by the original author.

TL;DR

Fix this in the anomaly detector by acting on the exact message first: inspect the raw file or payload at the failure point, fix encoding, quoting or header duplication there, and parse with a tolerant reader that logs skipped rows. 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.

agent couldn't parse metric export CSV error failed parsing failure

Use this when

• The operation in the anomaly detector fails with this exact message: agent couldn't parse metric export CSV error failed parsing failure.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check 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 anomaly detector, and copy the full message plus the item, user or metric 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: inspect the raw file or payload at the failure point, fix encoding, quoting or header duplication there, and parse with a tolerant reader that logs skipped rows. Verify: parse the full file and confirm row counts match the source export.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, 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 counts, decisions or alerts against the source in the anomaly detector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the anomaly detector 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

Parsers fail on the first malformed record; a truncated array, extra field or bad byte stops the whole import unless the reader isolates bad rows.

Variant phrasings

agent couldn't parse metric export CSV error failed parsing failure

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: agent couldn't parse metric export CSV error failed parsing failure

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

the anomaly detector troubleshooting for this failure

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 anomaly detector at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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

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

Thread query: agent couldn't parse metric export CSV error failed parsing failure

TL;DR: Fix this in the anomaly detector by acting on the exact message first: inspect the raw file or payload at the failure point, fix encoding, quoting or header duplication there, and parse with a tolerant reader that logs skipped rows. 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.

Not specified by the original author.

TL;DR

Fix this in scorecard import agent workflow by acting on the exact message first: open the Gainsight usage CSV directly, find the rows with shifted columns from unquoted commas in names or notes, re-export or repair with proper quoting, align the header to the scorecard import template, and parse a hundred rows cleanly before the full import. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.

parser failed on Gainsight usage CSV export for import usage data into the scorecard

Use this when

• The operation in scorecard import agent workflow fails with this exact message or symptom: parser failed on Gainsight usage CSV export for import usage data into the scorecard.
• The same failure repeats on retry with unchanged inputs.
• Scoring, alerting or routing is blocked until this item completes.

Not for this skill when

• The message is an 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 quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in scorecard import agent workflow, and copy the full message plus the account, measure or job involved into the run notes. Verify: the error is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this error: open the Gainsight usage CSV directly, find the rows with shifted columns from unquoted commas in names or notes, re-export or repair with proper quoting, align the header to the scorecard import template, and parse a hundred rows cleanly before the full import. Verify: the smallest failing scope now completes, or the named account, measure or job behaves as the fix predicts.
3. Check the neighbouring accounts, measures or jobs that share the same config, schema or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in scorecard import agent workflow 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.
5. Compare the result counts, scores or status against the source in scorecard import agent workflow so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
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

Usage exports contain free text with commas that shift columns when quoting is lost, and the parser fails at the first shifted row while the header looks correct.

Variant phrasings

parser failed on Gainsight usage CSV export for import usage data into the scorecard

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - parser failed on Gainsight usage CSV export for import usage data into the scorecard error parsing failure

The how-to phrasing for the same failure in scorecard import agent workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

scorecard import agent workflow troubleshooting for this failure

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.

Edge cases

• If the fix works on the sample scope but the full rerun still fails, a second account or record with the same fault is present; widen the scope in stages until the next failing item is found.
• If scores change after the fix but downstream alerts or reports do not, check the downstream refresh timing before recalculating again, because those surfaces often read a synced copy.
• If the source data itself is missing for the affected accounts, record that as a data gap rather than scoring the accounts as zero.

Compatibility: scorecard import agent workflow 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/pst_w2UqgetJSTa2RZHLj1vZtA

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

Thread query: parser failed on Gainsight usage CSV export for import usage data into the scorecard error parsing failure

TL;DR: Fix this in scorecard import agent workflow by acting on the exact message first: open the Gainsight usage CSV directly, find the rows with shifted columns from unquoted commas in names or notes, re-export or repair with proper quoting, align the header to the scorecard import template, and parse a hundred rows cleanly before the full import. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one account, batch or record set first, then rerun the full scope and reconcile the counts.