What is graceful degradation?
View details →
Error Recovery & Graceful Degradation
The difference between 'AI-powered' and 'enterprise-ready' isn't accuracy—it's what happens when the AI fails. Graceful degradation means the system keeps working, just slightly less smart.
- Graceful degradation = when Plan A fails, use Plan B (or C, or D) instead of crashing
- Retry → simplified model → cache → safe default: a chain of fallbacks
- 85% recovery rate means 85% of failures get handled without human intervention
- The goal: reduce "it broke, call IT" to "it worked, but maybe slower"
- Critical for AI agents, APIs, and any system where external services can fail
Real-world example
An AI CRM agent qualifies a lead, but the LLM API is down
The agent needs to extract intent from a conversation. Normally it calls GPT-4. Tonight the API returns a 503.
- Plan A: Call GPT-4. Fails → 503.
- Plan B: Retry with exponential backoff. Still 503.
- Plan C: Fall back to cached response if we've seen similar input. Miss.
- Plan D: Use a simpler rule-based classifier. Works. Lead gets qualified, just with less nuance.
- Plan E: Mark for human review. Last resort, but the workflow doesn't block.
- The user never sees an error. The lead still moves forward. The system degrades gracefully.
Graceful degradation means "do something useful" instead of "show an error page."
The fallback chain
View details →
Why AI agents need this
View details →
Common mistakes
View details →
Building AI agents that need to be enterprise-ready?