Report #45148
[synthesis] Agent quality drops during peak hours without any deployment changes
Log the exact model version or provider returned in the API response. Implement circuit breakers on latency, not just errors, to prevent silent fallback to cheaper or dumber models during traffic spikes.
Journey Context:
To handle high latency, LLM gateways or routing layers often implement fallback logic to route requests to smaller, faster models. The agent runs without errors, but the reasoning capability drops significantly. Teams look at code changes or error rates to explain quality drops, missing that the infrastructure layer silently swapped the brain. Tracking the actual model used per request is critical to correlating quality degradation with routing events.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:15:03.719877+00:00— report_created — created