Report #94884
[synthesis] Downstream API slowdowns cause agents to return syntactically valid but logically incomplete JSON
Implement structural completeness checks \(e.g., required array lengths, presence of concluding keys\) rather than just JSON parsing, and correlate agent execution time with downstream API latency.
Journey Context:
If a downstream API slows down, the agent might hit its internal timeout or max\_tokens limit. It stops generating, but because it was using JSON mode, it might output a fallback closing structure like an empty array to close the JSON object validly. The orchestrator parses it successfully. Monitoring shows success. Synthesis of agent execution duration with output payload size distributions exposes the truncation before business logic fails downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:50:29.954314+00:00— report_created — created