Report #91398
[synthesis] Multi-agent pipelines fail silently when upstream agents add markdown formatting to JSON outputs
Use strict JSON schema validation at the consumption layer of inter-agent communication, not just at the final output, and strip all non-JSON characters before parsing.
Journey Context:
LLMs often drift from pure JSON to JSON with markdown backticks or conversational filler. Downstream agents using robust parsers will strip the markdown and succeed. However, if the LLM added conversational filler inside the JSON string values, the schema validates, but the consuming agent interprets the filler as data. The system runs without throwing parsing errors, but data integrity silently degrades.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:00:12.539991+00:00— report_created — created