orpc-client-retry

Retry failed oRPC client calls with configurable policies.

8|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ali-master/skills --skill orpc-client-retry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orpc-client-retry
Source: https://github.com/ali-master/skills/tree/main/skills/orpc-client-retry
Command: npx skills add https://github.com/ali-master/skills --skill orpc-client-retry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @orpc/client/fetch, @orpc/client/plugins, and includes scripts (resource) components.

What problem does it solve?

This Skill automatically retries failed oRPC client calls, reducing the risk of errors in your application.

Core Features & Use Cases

  • Automatic Retry: Retry failed client calls when errors occur.
  • Customizable: Set retry policies based on the method path and error type.
  • Use Case: For applications with high availability requirements, such as API gateways or microservices, this Skill helps maintain robust communication and error handling.

Quick Start

Add the orpc-client-retry skill to your project and configure the retry policy for specific methods.

Frequently Asked Questions about orpc-client-retry

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

FAQPage Schema
How do I automatically retry failed oRPC client calls?

You can automatically retry failed oRPC client calls by configuring a retry policy that intercepts request errors and re-executes the call. This reduces the risk of application errors and improves fault tolerance.

Can I customize retry policies based on method paths and error types in oRPC?

Yes, you can customize retry policies based on oRPC method paths and error types. This allows you to target specific API endpoints and failure conditions, enhancing API stability and reliability for high availability applications.

How do I add fault tolerance to a microservices architecture using oRPC?

To add fault tolerance to a microservices architecture using oRPC, implement automatic client call retries. This maintains robust communication and handles errors automatically, reducing the risk of failures in API gateways or microservices.

Does the oRPC retry client require specific dependencies?

Yes, implementing the oRPC retry client requires specific dependencies, namely @orpc/client/fetch and @orpc/client/plugins. These packages provide the necessary client and plugin interfaces to intercept and retry failed calls.

What is the best way to handle API stability and resilience in oRPC service architectures?

The best way to handle API stability and resilience in oRPC service architectures is to configure automatic retry policies for failed client calls. This approach targets specific method paths and error types to maintain robust communication.