Graceful Degradation Path
When the primary pathway fails, the agent falls back to a reduced-capability alternative rather than returning nothing.
This page is the complete instruction page for one pattern called "Graceful Degradation Path." It explains the problem this pattern solves, the idea behind the solution, when you should (and should not) use it, and what happens afterward, both the good effects and the costs.
This matters because building AI agents is not just about making them clever. It is also about making them safe and predictable. Following a well-tested pattern like this one helps avoid common mistakes, and shows you exactly which safety rules and regulations it connects to, listed under "Standards Mesh" on this page.
Context
A RAG agent whose index is down can still answer from general knowledge with a caveat. A scheduling agent without calendar access can still draft the invite. Returning "error" is rarely the right ending.
Problem
Binary success/failure ignores the space of useful-but-reduced responses.
Forces
- Capability fidelity vs availability
- User expectation management
Solution
Define tiered fallback paths: primary → secondary → tertiary → human. Each tier is clearly labelled to the user (e.g. "knowledge-base unavailable; answering from general knowledge: please verify"). Fallback decisions are logged for observability.
Where this pattern acts in the two lifecycles
07 Terminate. Exit conditions, HITL escalation, handoff. 6 of 61 catalogue patterns act at this stage.
05 Operate & Monitor. Runtime telemetry, drift detection. 18 of 61 catalogue patterns act at this stage.
Stages and counts from the catalogue data. The Runtime lens is the loop the agent runs each turn; the AgentOps lens is the lifecycle the team runs the agent through. See the Matrix for every pattern at each stage.
Applicability
- User-facing agents
- Agents with critical external dependencies
- Reliability-sensitive deployments
Anti-Patterns
- Silently falling back without telling the user
- "Fallback" that is the same path with worse prompt
Consequences
- +Resilience with honesty
- +Reduced mean time to useful
- −Designing fallback paths is work
- −Users may conflate tiers
