Retry HTTP requests automatically using server-sent Retry-After headers.
npx skills add https://github.com/ali-master/skills --skill orpc-retry-after
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
This Skill helps manage rate limiting and temporary server unavailability by automatically retrying requests based on server Retry-After headers.
Add the oRPC Retry After Plugin to your oRPC client configuration to automatically handle retries.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
ali-masterIntegrates OpenAPI-compliant APIs into oRPC clients via HTTP/Fetch.
neoknDesign RESTful APIs with resource-based URLs, HTTP methods, and status codes.
dtsongDesign REST/RPC endpoint contracts with TypeScript types and error handling.
vtexdocsConfigure retry logic with exponential backoff for VTEX marketplace API calls.
