Operational Playbooks provides cross-error incident runbooks for recurring production failures such as API timeouts, authentication breakdowns, CORS policy mismatches, and rate-limit recovery. Each playbook lays out triage checkpoints, containment actions, verification criteria, and prevention controls in execution order. Use these guides during active response windows when speed and correctness both matter.
Showing 1-10 of 10.
Use this playbook to separate invalid upstream responses from upstream wait expiration and deadline exhaustion, and apply timeout budgets, safe retries, and circuit-breaker controls safely.
Use this playbook to separate origin-side 500 failures from temporary 503 dependency or capacity outages, then apply safe retry and escalation paths.
Use this playbook to triage policy-based access denials after authentication succeeds, isolate the deny layer, and apply least-privilege remediation safely.
Use this playbook to separate missing, expired, or invalid identity proof from authorization and transport failures, and apply credential-source-correct fixes safely.
Use this playbook to separate true write conflicts from stale precondition failures, then apply safe re-fetch, optimistic-lock, and retry choices.
Use this playbook to separate browser-enforced cross-origin policy failures from server-side CORS header and route defects and apply strict origin and credential controls safely.
Use this playbook to separate transient throttling from hard quota exhaustion and apply retry, traffic-shaping, and quota-capacity fixes safely.
Use this playbook to separate temporary missing-resource lookups from permanent removals, then fix scope, lifecycle, and identifier drift safely.
Triage 500, gRPC UNKNOWN, and cloud InternalError fast: preserve correlation IDs, separate transient provider faults from app bugs, and apply safe retries.
Use this playbook to separate malformed-request failures from semantic validation failures, then fix request contracts without broad server-side bypasses.