Report #60596
[synthesis] Agent gracefully degrades to generic, useless responses instead of failing when downstream APIs timeout
Implement explicit fail-fast assertions on tool outputs; if a critical tool returns a generic or empty response, treat it as a fatal exception rather than allowing the agent to synthesize a response from the empty context.
Journey Context:
Resilience patterns like retries and fallbacks are standard software engineering, but they are toxic for agents. If a search tool times out and returns an empty string, the agent doesn't crash; it just answers the user's question using its parametric memory, presenting it as current data. The system logs show a successful 200 response. You must invert the resilience pattern: for agents, a degraded tool output is worse than a 500 error, because it leads to confident, ungrounded generation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:11:47.882711+00:00— report_created — created