Error Handling Protocols

Diagnose and recover from API failures and infrastructure issues in trading systems.

38|9|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/IgorGanapolsky/trading --skill error-handling-protocols
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Error Handling Protocols
Source: https://github.com/IgorGanapolsky/trading/tree/main/.claude/skills/error_handling_protocols
Command: npx skills add https://github.com/IgorGanapolsky/trading --skill error-handling-protocols

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies robust error-handling practices to improve reliability.

Core Features & Use Cases

  • API failure handling: retry with backoff.
  • Timeouts & rate limits: defined strategies per source.
  • Logging & monitoring: Sentry integration and alerting.
  • Graceful degradation: fallback strategies for data loss.

Quick Start

Implement these protocols in your data flow and trading commands.

Frequently Asked Questions about Error Handling Protocols

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

FAQPage Schema
How do I handle API failures and timeouts in my trading system?

API failure handling implements retry logic with exponential backoff strategies. Define timeout thresholds and rate-limit responses per data source, then apply automatic retries with graceful degradation to maintain system reliability when sources fail or become unavailable.

What's the best way to implement graceful degradation when data sources go down?

Graceful degradation uses fallback strategies and data caching to continue operations when primary sources fail. Prioritize available data sources, cache recent results, and execute workflows with reduced data rather than failing completely, ensuring fault-tolerant behavior across retrieval and processing.

How should I log and monitor infrastructure failures and outages?

Standardized logging with Sentry integration and alerting provides auditability and real-time visibility into failures. Log all retries, timeouts, and fallback decisions with contextual metadata, enabling rapid diagnosis of infrastructure issues and automatic notifications when thresholds are exceeded.

When do I need fail-fast decision logic versus retry strategies?

Fail-fast logic applies to unrecoverable errors and rate-limit responses to prevent cascading failures. Use retries with backoff for transient failures like timeouts and temporary unavailability, and fail immediately for permanent errors or exhausted retry budgets to maintain system responsiveness.

Can I use source prioritization to handle multiple data provider failures?

Source prioritization ranks available data providers and switches to fallbacks when primary sources fail. The system automatically selects the next available source based on reliability history and current status, delivering fault-tolerant data retrieval without manual intervention.