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.
Build a CometAPI SSE stream parser that preserves event boundaries, validates JSON fragments, and rejects truncated output safely.
A practical error taxonomy for deciding when an LLM gateway should retry, fail over, or stop immediately.
Roll out versioned CometAPI fallback policies across gateway replicas without mixed routing decisions, stale configuration, or unsafe promotion.
Use latency feedback, bounded queues, and early load shedding to keep changing LLM workloads from exhausting gateway and upstream capacity.
A protocol-aware runbook for recovering LLM requests after HTTP/2 GOAWAY or 421 responses without causing duplicate execution.
Design LLM API burn-rate alerts that separate urgent incidents from slow reliability erosion and guide safer operator action.