Report #71325
[synthesis] Agent exhausts token limits or context windows on tasks it previously completed successfully
Implement exponential backoff with a circuit breaker on tool execution time, and monitor the ratio of tool execution time to total agent run time.
Journey Context:
A downstream API slows down by just a few hundred milliseconds—not enough to throw a timeout error, but enough to push the agent's planning step out of sync. The agent calls the tool, gets a delayed response, assumes it missed the output, and calls it again. This loop silently consumes the context window until the agent fails with a generic context length exceeded error, masking the root cause \(latency\) as a token limit issue. Combining distributed systems reliability patterns with LLM context management reveals the true cause.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:17:39.900393+00:00— report_created — created