error-recovery

Apply retry, backoff, fallback, and escalation patterns to failing operations.

413|64|Updated Feb 7, 2023

Search Tags:#resilience #error-recovery #escalation #fallback #retry #backoff

Ready to run

npx skills add https://github.com/christianhelle/refitter --skill error-recovery-christianhelle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/christianhelle/refitter/tree/main/.copilot/skills/error-recovery
Command: npx skills add https://github.com/christianhelle/refitter --skill error-recovery-christianhelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.

Core Features & Use Cases

Retry with Backoff: wait and retry with exponential backoff to recover from transient errors.
Fallback Alternatives: switch to alternative approaches when a primary method fails.
Diagnose-and-Fix: collect error context and guide targeted remediation.
Escalate with Context: hand off detailed failure summaries to human experts when needed.
Graceful Degradation: continue delivering partial results when non-critical steps fail.

Quick Start

Apply standard recovery patterns to a failing operation and return a resilient, documented outcome.

Frequently Asked Questions about error-recovery

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

FAQPage Schema

How do I implement retry with exponential backoff for failing API calls?▼

Retry with exponential backoff for failing API calls involves waiting progressively longer between attempts to recover from transient errors. This approach applies deterministic retry logic to reduce downtime in automated workflows.

What is graceful degradation when a build task fails?▼

Graceful degradation when a build task fails means continuing to deliver partial results when non-critical steps fail. Instead of halting the entire workflow, the system adapts and returns what it can while logging the failure context.

How do I set up fallback alternatives for failed tool executions?▼

Fallback alternatives for failed tool executions switch execution to secondary methods when a primary approach fails. This pattern allows automated workflows to proceed by selecting a viable alternative path instead of reporting a hard failure.

What's the best way to escalate failed operations with error context?▼

Escalating failed operations with error context requires handing off detailed failure summaries to human experts. This ensures the receiving expert gets diagnostic information and targeted remediation guidance rather than a generic error message.

Can I use error recovery patterns for automated build tasks and tool executions?▼

Yes, error recovery patterns apply to automated build tasks, tool executions, and API calls. The patterns identify failing operations and apply standard recovery logic such as retries, fallbacks, and diagnostic fixes across these workflows.

When should I not use retry patterns for transient errors?▼

Retry patterns for transient errors should not be used when failures are deterministic and non-transient. If an operation fails due to invalid inputs or permissions, retrying will not resolve the issue and will only increase system load.