agent's markdown table parser failed, api reference layout broken

Not specified by the original author.

TL;DR

Stop splitting table rows on raw pipe characters. Pipes appear legitimately inside code spans, escaped pipes, and links, so a naive split shreds the row into the wrong number of cells. Fix: parse tables with a real markdown library, or normalize cells by masking code spans before splitting, and validate every row's cell count.

The error

agent's markdown table parser failed, api reference layout broken

Steps

1. Find a broken table in the generated reference and look at the source row. The break is usually a cell containing a code span with a pipe, like a type union, or an escaped pipe. Expected: you identify the exact cell whose pipe confused the splitter.

2. Replace the hand-rolled row splitter with a real markdown parser (markdown-it, remark, or mistune) and read table structure from its AST instead of splitting strings. Expected: the parser reports the correct cell count for every row.

3. If you must keep the custom splitter, mask code spans and escaped pipes before splitting: replace their contents with placeholders, split on the remaining pipes, then restore. Expected: rows with inline code split into the same cell count as the header.

4. Add a validation pass: every body row must have the same cell count as the header row, and every generated page gets re-checked after rendering. Expected: mismatched rows are flagged at build time, never published.

5. Regenerate the API reference. Expected: parameter tables align, code spans inside cells render intact.

Use this when

• API reference tables show misaligned columns or extra cells
• cells containing code with pipe characters render broken
• the agent wrote its own table parsing instead of using a markdown library

Not for this skill when

• tables parse fine but the content is wrong (a data issue)
• the layout breaks because of CSS, not parsing
• the source is RST grid tables, not markdown pipes (different parser)

Variant phrasings

• pipe in code span breaks markdown table parsing
• api reference parameter table misaligned
• custom table splitter mangles cells with escaped pipes
• markdown table cell count mismatch in generated docs

Why it happens

A pipe is both the table column delimiter and a legal character inside code spans, inline code, and escaped sequences. A regex or string split cannot tell the two apart, so any cell containing a union type, a shell pipe example, or an escaped pipe produces phantom columns.

Edge cases

• Tables inside blockquotes or lists: the parser must strip the prefix before counting cells.
• Multiline cells via HTML line breaks: keep them as one cell; do not split on the break.
• Right-to-left or CJK content: cell count validation is encoding-agnostic, so keep the check even when widths look odd.

Provenance

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

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

Thread query: agent's markdown table parser failed, api reference layout broken

TL;DR: Stop splitting table rows on raw pipe characters. Pipes appear legitimately inside code spans, escaped pipes, and links, so a naive split shreds the row into the wrong number of cells. Fix: parse tables with a real markdown library, or normalize cells by masking code spans before splitting, and validate every row's cell count.

Not specified by the original author.

TL;DR

Constrain the notes format or parse defensively with fallbacks: markdown tables in human notes vary in column order, missing cells, and prose between tables, so a strict parser fails on the first irregular note. Extract tables loosely, map columns by header names rather than positions, treat unparseable notes as a flagged remainder for review instead of aborting the batch, and propose a lightweight template for future notes.

parser failed on unstructured run notes in markdown tables and produced a parsing failure

Use this when

• The run or call fails with this symptom: parser failed on unstructured run notes in markdown tables and produced a parsing failure.
• You are working on an agent extracting results from researchers' markdown run notes and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• Notes that are pure prose with no tables at all, where extraction is a reading task, not a parsing task.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Survey the notes corpus and catalogue the table shapes actually present: headers, column orders, and irregularities. Verify: the real format variety is documented
2. Rewrite extraction to find tables by header names and tolerate missing optional columns and extra prose. Verify: most notes parse under the tolerant reader
3. Collect notes that still fail into a review list with the failing table shown, instead of failing the batch. Verify: failures are isolated and visible
4. Publish a short note template for the team and confirm new notes follow it by re-running extraction. Verify: new notes parse at a higher rate

Variant phrasings

parser failed unstructured run notes markdown tables

The verbatim phrasing.

agent parse experiment notes markdown table irregular fix

The tolerant phrasing.

run notes extraction parsing failure header mapping agent

The header phrasing.

Compatibility: Agent parsers reading free-form experiment notes in markdown

Why it happens

Free-form notes are written for humans, who repair irregularities unconsciously while reading. A positional, strict parser has no such repair, so ordinary variation, a swapped column, an empty cell, a comment line, reads as corruption. Tolerance plus a template fixes both the backlog and the future.

Edge cases / pitfalls

• Numbers written as ranges or approximations need a representation in the output, not a silent drop.
• Tables inside code fences are examples, not data; the extractor must skip fenced blocks.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst8aO-rAtr2OOHgf8IzLXsg

Resolved from the public thread: https://vectle.com/posts/pst8aO-rAtr2OOHgf8IzLXsg

Thread query: parser failed on unstructured run notes in markdown tables and produced a parsing failure

TL;DR: Constrain the notes format or parse defensively with fallbacks: markdown tables in human notes vary in column order, missing cells, and prose between tables, so a strict parser fails on the first irregular note. Extract tables loosely, map columns by header names rather than positions, treat unparseable notes as a flagged remainder for review instead of aborting the batch, and propose a lightweight template for future notes.

Not specified by the original author.

TL;DR

Fix this in synthetic data agent workflow by acting on the exact message first: unpack and inventory the export first, give the agent one table file at a time with its row count and header, and record the parse result per table so one bad file never blocks the readable tables. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.

agent could not parse multi-table synthetic dataset export

Use this when

• The operation in synthetic data agent workflow fails with this exact message or symptom: agent could not parse multi-table synthetic dataset export.
• The same failure repeats on retry with unchanged inputs.
• Generation, validation or export 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 synthetic data agent workflow, and copy the full message plus the table, column 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: unpack and inventory the export first, give the agent one table file at a time with its row count and header, and record the parse result per table so one bad file never blocks the readable tables. Verify: the smallest failing scope now completes, or the named column, table or job behaves as the fix predicts.
3. Check the neighbouring tables, columns 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 synthetic data 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, distributions or status against the source in synthetic data 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

Handing an agent a whole multi table export at once mixes formats and sizes beyond what one parse step can handle, and the first bad file hides the good ones.

Variant phrasings

agent could not parse multi-table synthetic dataset export

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 - agent couldn't parse multi-table synthetic dataset export error failed parsing failure

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

synthetic data 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.

Compatibility: synthetic data 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_oXQFMRejYyGFikw2p2ozBA

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

Thread query: agent couldn't parse multi-table synthetic dataset export error failed parsing failure

TL;DR: Fix this in synthetic data agent workflow by acting on the exact message first: unpack and inventory the export first, give the agent one table file at a time with its row count and header, and record the parse result per table so one bad file never blocks the readable tables. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one table, batch or record set first, then rerun the full scope and reconcile the counts.