Circuit breakers

Circuit breakers temporarily exclude failing upstream transports and admit recovery attempts before returning them to ordinary routing. HTTP and WebSocket health are tracked separately.

State	Meaning
Closed	Normal admission, subject to the other routing gates.
Open	Ordinary traffic is excluded until recovery is permitted.
Half-open	Limited recovery traffic determines whether service has recovered.

A closed circuit alone does not prove that a provider is currently eligible. Connection state, rate-limit cooldowns, lag, method restrictions, and request parameters can still exclude it.

Rate limits and shared providers

Rate-limit backoff is a separate signal from circuit failure. A provider can be temporarily rate limited while its circuit remains closed. Identical upstreams shared across profiles share runtime signals; creating another profile does not bypass the provider’s real quota. Inspect the affected transport and region. An aggregate warning may represent only part of the deployment. Do not interpret a regional problem as proof that every region is unavailable.

Configuration

Circuit Breaker Defaults

config :lasso, :circuit_breaker,
  failure_threshold: 5,     # Aggregate failure threshold; category thresholds also apply
  success_threshold: 2,     # Consecutive successes to close
  recovery_timeout: 60_000  # Base ms before half-open; category/backoff rules also apply

Circuit settings take effect when provider instances start; restart Lasso after changing application configuration. YAML reload does not restart existing circuit breakers. See Profiles for sharing behavior and Provider capabilities for error rules.

Get Started

Core Concepts

Configuration

Deployment

Observability

Advanced

Circuit breakers

Rate limits and shared providers

Configuration

Circuit Breaker Defaults

​Rate limits and shared providers

​Configuration

​Circuit Breaker Defaults

Rate limits and shared providers

Configuration

Circuit Breaker Defaults