Error Recovery Patterns Skill

Guide retry, circuit breaker, fallback, and rollback patterns for resilient systems.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill error-recovery-patterns-skill-fabioc-aloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Error Recovery Patterns Skill
Source: https://github.com/fabioc-aloha/AIRS_Data_Analysis/tree/main/.github/skills/error-recovery-patterns
Command: npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill error-recovery-patterns-skill-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides strategies and patterns to handle failures gracefully, ensuring system stability and minimizing disruption when errors occur.

Core Features & Use Cases

  • Recovery Hierarchy: Outlines a structured approach to error handling: Prevent, Detect, Contain, Recover, Learn.
  • Retry Mechanisms: Defines rules for when to retry operations (e.g., network timeouts, rate limits) and when not to (e.g., validation errors, auth failures), including exponential backoff with jitter.
  • Circuit Breaker: Implements the circuit breaker pattern to prevent repeated calls to failing services.
  • Fallback Strategies: Offers patterns like default values, cached data, or degraded service for when primary operations fail.
  • Rollback Patterns: Details methods for undoing operations, such as database transactions, sagas, or feature flags.
  • Error Boundaries: Emphasizes containing failures to prevent cascading issues.

Quick Start

Use the error recovery patterns skill to implement a retry mechanism with exponential backoff for a failing API call.

Frequently Asked Questions about Error Recovery Patterns Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement retry logic with exponential backoff for failing API calls?

Use retry mechanisms with exponential backoff and jitter for failing API calls to handle transient network timeouts or rate limits. Avoid retrying validation errors or authentication failures to prevent compounding failures.

What is a circuit breaker pattern and when should I use it for error handling?

A circuit breaker pattern stops repeated calls to failing services to prevent cascading failures. Use it for error handling when a downstream service is unstable, containing the failure and allowing the system to recover.

What's the best way to handle fallback strategies when primary operations fail?

The best way to handle fallback strategies is to provide default values, cached data, or degraded service modes. This ensures system stability and minimizes disruption when primary operations fail.

How do I rollback distributed transactions and atomic operations?

Rollback distributed transactions and atomic operations using database transactions, sagas, or feature flags. These patterns undo operations to maintain data consistency when errors occur.

When should I not use retry mechanisms for error recovery?

Do not use retry mechanisms for validation errors or authentication failures. Retrying these deterministic errors wastes resources and can degrade system stability instead of enabling recovery.