agent's amount parser broke on european decimal commas error

Not specified by the original author.

TL;DR

European receipts write 1.234,56 where US receipts write 1,234.56, and a naive parser reads the wrong value. Normalize amounts using the receipt's locale: treat the last separator as the decimal mark, strip the thousand separators, then parse.

Error

agent's amount parser broke on european decimal commas

Steps

1. Detect the locale signals on the receipt: country, currency symbol, and vendor address. Expected: a likely number format.
2. Normalize: take the last comma or period as the decimal separator and remove all other separators. Expected: a plain digits-and-decimal string.
3. Parse the normalized string to a decimal type, never a float. Expected: an exact amount.
4. Sanity-check the result against the receipt total's magnitude (a coffee is not 123,456). Expected: absurd values get flagged.
5. Log the raw and normalized forms for every parsed amount. Expected: an audit trail for the normalization.

When to use

• Amounts with European decimal commas parse wrong.
• Parsed totals are off by orders of magnitude.

When not to use

• The currency symbol is misread (a symbol-mapping problem).
• The amount is missing (an OCR problem).

Tool compatibility

• Custom agent amount parsing; decimal arithmetic libraries.

Variant phrasings

Decimal comma misparsed

Same failure, shorter wording.

European number format broke parser

Names the format directly.

Why it happens

Separators swap roles across locales: the comma groups thousands in the US and marks decimals in Europe. A parser with one assumption inverts the value.

Provenance

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

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

Thread query: agent's amount parser broke on european decimal commas error

TL;DR: European receipts write 1.234,56 where US receipts write 1,234.56, and a naive parser reads the wrong value. Normalize amounts using the receipt's locale: treat the last separator as the decimal mark, strip the thousand separators, then parse.

Not specified by the original author.

TL;DR

Fix this in Broken redirect crawl agent by acting on the exact symptom first: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Parser failed on the redirect map CSV for crawling the help center for broken redirects

Use this when

• Work in Broken redirect crawl agent shows this exact symptom: Parser failed on the redirect map CSV for crawling the help center for broken redirects.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Broken redirect crawl agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Broken redirect crawl agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Parser failed on the redirect map CSV for crawling the help center for broken redirects

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - parser failed on redirect map CSV for crawling the help center for broken redirects error parsing failure

The how to phrasing for the same problem in Broken redirect crawl agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Broken redirect crawl agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Redirect maps exported from a spreadsheet often carry quoted addresses containing commas, and a naive split on commas broke rows into the wrong fields.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Broken redirect crawl agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: parser failed on redirect map CSV for crawling the help center for broken redirects error parsing failure

TL;DR: Fix this in Broken redirect crawl agent by acting on the exact symptom first: detect the CSV delimiter and quoting from the header row, validate that every row has a source and a target address, reject malformed rows into a small error list, and parse the clean rows again. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in moderation queue triage agent by acting on the exact problem first: inspect the first lines of the search query log file, detect its real delimiter and quoting, skip and quarantine malformed lines instead of failing the file, and parse a hundred lines cleanly before running triage on the whole log. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Parser failed on the forum search query log during queue triage

Use this when

• The operation in moderation queue triage agent fails with this exact message or symptom: Parser failed on the forum search query log during queue triage.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in moderation queue triage agent, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: inspect the first lines of the search query log file, detect its real delimiter and quoting, skip and quarantine malformed lines instead of failing the file, and parse a hundred lines cleanly before running triage on the whole log. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 moderation queue triage agent 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 or status against the source in moderation queue triage agent 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 problem, the fix applied and the evidence of success.

Why it happens

Log exports mix quoted queries containing commas with plain lines, so a parser set for one shape fails on the other and blocks triage that depends on the log.

Variant phrasings

Parser failed on the forum search query log during queue triage

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

How to fix - parser failed on forum search query log for triage the moderation queue error parsing failure

The how to phrasing for the same failure in moderation queue triage agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

moderation queue triage agent 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 small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: moderation queue triage agent at current versions, plus the admin console, moderation queue or API 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_md9C8sJiojTqoB0wU91TJQ

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

Thread query: parser failed on forum search query log for triage the moderation queue error parsing failure

TL;DR: Fix this in moderation queue triage agent by acting on the exact problem first: inspect the first lines of the search query log file, detect its real delimiter and quoting, skip and quarantine malformed lines instead of failing the file, and parse a hundred lines cleanly before running triage on the whole log. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.