Circuit Breaker Pattern

The circuit-breaker pattern allows AI agents to detect when a specific tool or API call is failing repeatedly and automatically stop invoking it for a set duration. This prevents cascading errors, saves computational resources, and forces the agent to switch strategies or retry later once the service recovers.

When to use it

• Failing External APIs: Stop an agent from looping endlessly when a weather or payment API returns 503 errors.
• Rate Limit Protection: Halt requests immediately after hitting a quota limit to avoid temporary bans.
• Unstable Integrations: Pause interactions with flaky third-party services while the system stabilizes.
• Resource Conservation: Prevent wasting tokens and compute cycles on doomed operations during high-load periods.

Key capabilities

• Automatic invocation halting after consecutive failures.
• Configurable cooldown periods before retry attempts resume.
• State tracking to distinguish between transient and permanent errors.
• Graceful degradation by switching to fallback tools or alternative logic.

Example prompts

• "Implement a circuit breaker for my weather API that stops requests after 3 consecutive failures and retries after 5 minutes."
• "Add a circuit breaker pattern to prevent my agent from spamming the payment gateway during high traffic."
• "Configure a fallback mechanism that activates when the primary search engine returns errors too frequently."

Tips & gotchas

Ensure you define clear thresholds for failure counts and cooldown durations; setting them too low may cause unnecessary interruptions, while setting them too high delays recovery. Monitor the underlying service health to distinguish between temporary glitches and permanent outages before relying on automatic fallbacks.