orpc-retry-after

Retry HTTP requests automatically using server-sent Retry-After headers.

8|Updated Mar 3, 2026

Search Tags:#API integration #rate limiting #retry logic #HTTP requests #server unavailability

Ready to run

npx skills add https://github.com/ali-master/skills --skill orpc-retry-after

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orpc-retry-after
Source: https://github.com/ali-master/skills/tree/main/skills/orpc-retry-after
Command: npx skills add https://github.com/ali-master/skills --skill orpc-retry-after

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage rate limiting and temporary server unavailability by automatically retrying requests based on server Retry-After headers.

Core Features & Use Cases

Automated Retries: Automatically retries requests when encountering rate limiting (429) or server unavailability (503).
Custom Conditions: Allows custom conditions for retries, not limited to specific status codes.
Use Case: If your application is subject to API rate limits, this Skill can help ensure your requests are not dropped and your application remains responsive.

Quick Start

Add the oRPC Retry After Plugin to your oRPC client configuration to automatically handle retries.

Frequently Asked Questions about orpc-retry-after

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

FAQPage Schema

How do I handle API rate limiting and HTTP 429 errors automatically?▼

Handle API rate limiting by automatically retrying HTTP requests based on the server-sent Retry-After header. This ensures your application pauses for the exact duration specified by the API before attempting the request again.

What is the best way to retry HTTP requests when a server is unavailable?▼

The best way to manage temporary server unavailability is to configure your client to automatically retry HTTP requests upon receiving a 503 status code. This allows the application to recover seamlessly once the server is back online.

Can I define custom retry conditions beyond HTTP 429 and 503 status codes?▼

Yes, you can define custom conditions for retries that are not limited to specific status codes like 429 or 503. This flexibility allows you to trigger retries based on other server responses or application-specific logic.

How do I add retry logic to my oRPC client configuration?▼

Add the retry logic to your client configuration by integrating the oRPC Retry After Plugin. This automatically handles request retries for rate limits and server outages without requiring manual intervention in your code.

Why does my application drop API requests when hitting rate limits?▼

Applications drop API requests during rate limits if they lack automated retry logic. Implementing a mechanism to read the Retry-After header and pause subsequent requests ensures your application remains responsive instead of failing immediately.

Are there limitations to using server Retry-After headers for request retries?▼

Using server Retry-After headers relies on the API server accurately providing this header during rate limiting or downtime. If the server omits this header during a 429 or 503 response, the automated retry mechanism may not know how long to wait.