Timeouts
Timeout budgets, retries, and safe fallback boundaries for LLM API calls.
Reliability Runbook
Practical guides for LLM API reliability and fallback engineering.
Failure Map
Use these notes to decide what to retry, route, stop, or escalate before production traffic is exposed.
Timeout budgets, retries, and safe fallback boundaries for LLM API calls.
How to identify quota behavior without hiding customer-impacting failures.
Decision rules for switching providers, models, or degraded modes.
Smoke tests and evidence requirements before calling a route production-ready.
Latest Runbook Notes
Historical archive entries remain available to readers while staying out of RSS, sitemap, and llms.txt.
Rotate LLM API credentials through explicit versions, canary checks, worker convergence, and provider revocation so old secret copies do not strand running consumers.
Stop authenticated CometAPI calls at unexpected redirects, preserve POST semantics, and review endpoint changes before resending credentials or prompts.
Preserve certificate verification, hostname identity, and deliberate trust-store selection when an LLM gateway changes routes during failover.
Control realtime LLM WebSocket reconnects with one reconnect owner, jittered backoff, session epochs, admission limits, and explicit replay rules.
A practical pattern for carrying one caller deadline through LLM retries and fallback providers while enforcing per-attempt limits and cancellation.
Build a trustworthy usage ledger for LLM streams that terminate before provider-reported token totals arrive.