Report #66248
[architecture] LLM outputs malformed JSON causing downstream agent pipeline crashes
Insert a strict JSON Schema validation layer between agents; reject non-conforming outputs and trigger retry with exponential backoff or escalation to a stronger model.
Journey Context:
Raw LLM outputs are probabilistic and frequently contain schema drift such as missing fields or incorrect types. Simple regex validation fails on nested structures, while 'gentle parsing' silently corrupts state downstream. Strict validation breaks the chain early, forcing explicit error handling. The tradeoff is increased latency due to validation overhead and potential retry loops, but system reliability dominates in multi-agent chains where one malformed packet poisons the entire workflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:40:30.314407+00:00— report_created — created