Jargonautica
Running It in Production

Fallback and Failover

What happens when the primary route fails. Providers have outages, rate limits bite, and requests time out. Deciding in advance whether to retry, switch to another model, serve a cached answer or degrade gracefully is what separates a brief blip from an incident.

Technical view

Strategies include cross-provider failover, which requires prompt and output-format compatibility testing in advance, downgrade to a smaller model, serving stale cached responses, and queueing for later processing. Behaviour should be observable, since silent fallback to a weaker model produces a quality regression nobody can explain. Fallback paths need their own evaluation, as they are exercised rarely and therefore rot.


Part of AI Terminology Index, section: Running It in Production.

How it connects

Fallback and Failover links to 6 other terms. The faint lines are links between those terms. See it in the full graph.

AI GatewayAI GatewayRate Limits and QuotasRate Limits and Quo…Observability and TracingObservability and T…Model RouterModel RouterCircuit BreakerCircuit BreakerService Level ObjectiveService Level Objec…Fallback and Failover