retry-strategies

Implement exponential backoff, circuit breakers, and bulkheads for external API retries.

6|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/daishiman/AIWorkflowOrchestrator --skill retry-strategies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retry-strategies
Source: https://github.com/daishiman/AIWorkflowOrchestrator/tree/main/.claude/skills/retry-strategies
Command: npx skills add https://github.com/daishiman/AIWorkflowOrchestrator --skill retry-strategies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides robust patterns for handling temporary failures in external API calls, preventing cascading failures and improving system availability. It solves the critical problem of unreliable distributed systems by implementing intelligent retry mechanisms and circuit breakers.

Core Features & Use Cases

  • Exponential Backoff: Implements a retry strategy that exponentially increases wait times between retries, reducing load on failing services.
  • Circuit Breaker: Prevents continuous requests to a failing service, allowing it to recover and protecting your system from cascading failures.
  • Bulkhead Pattern: Isolates resources to prevent a failure in one service from impacting others, enhancing overall system stability.
  • Timeout Management: Guides on setting appropriate connection, read, and total timeouts to prevent resource exhaustion.
  • Use Case: When integrating with a third-party payment gateway that occasionally experiences intermittent outages, use this skill to implement an Exponential Backoff retry strategy with a Circuit Breaker. This ensures your application automatically attempts to reprocess payments, gracefully handles prolonged outages, and prevents your system from being overwhelmed by retries.

Quick Start

Use the retry-strategies skill to design a retry policy for an external API call that might experience temporary network issues. Include Exponential Backoff with jitter and a maximum of 5 retries. Suggest a Circuit Breaker configuration to prevent cascading failures.

Frequently Asked Questions about retry-strategies

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

FAQPage Schema
How do I prevent cascading failures when calling unreliable APIs?

Implement a circuit breaker pattern to stop requests to failing services, allowing recovery time and protecting your system from cascading failures. Pair it with exponential backoff retry logic to handle transient errors intelligently without overwhelming the service.

What's the best way to handle temporary timeouts and rate limits in microservices?

Use exponential backoff with jitter to space retries over increasing intervals, reducing load on rate-limited services. Set appropriate connection, read, and total timeouts to prevent resource exhaustion while the service recovers from transient issues.

When should I use a bulkhead pattern in distributed systems?

Use bulkheads to isolate resources and prevent a failure in one service from impacting others. This containment strategy enhances overall system stability in microservice ecosystems where multiple services depend on each other.

How do I design a retry policy for external API integration?

Design a policy with exponential backoff, jitter, and a maximum retry count (typically 5). Add circuit breaker configuration to detect prolonged outages and stop retrying, preventing wasted resources and cascading failures.

Can I use retry strategies with third-party payment gateways?

Yes. Implement exponential backoff with circuit breaker logic to automatically retry failed payment requests during intermittent outages while gracefully handling prolonged service degradation without overwhelming the gateway.

What's the difference between timeout management and retry strategies?

Timeouts define how long to wait for a response before failing a single request; retries determine how many times and at what intervals to attempt the request. Together they prevent resource exhaustion and improve resilience in unreliable networks.