lokalise-incident-runbook

# Lokalise Incident Runbook ## Overview Rapid-response procedures for Lokalise-related incidents in production. Covers quick diagnostics (API health, token validity, rate limit status), triage for five common failure modes (missing translations, stale translations, API outage, file upload failures, OTA failures), fallback to cached translations, and communication templates for stakeholder notification. Designed to be executed under pressure — each section is self-contained. ## Prerequisites - `curl` and `jq` available on the responder's machine - Production Lokalise API token accessible (from secret manager or break-glass procedure) - `LOKALISE_PROJECT_ID` known (check your deployment config or Lokalise dashboard) - Access to application logs (Datadog, CloudWatch, GCP Logging, or equivalent) - Incident communication channel (Slack, PagerDuty, or equivalent) ## Instructions ### Step 1: Quick Diagnostics (Run First) Execute these three checks immediately to narrow the problem scope. Copy-paste into your terminal: ```bash #!/bin/bash # incident-diagnostics.sh — Run all three checks in sequence set -uo pipefail : "${LOKALISE_API_TOKEN:?Set LOKALISE_API_TOKEN before running diagnostics}" : "${LOKALISE_PROJECT_ID:?Set LOKALISE_PROJECT_ID before running diagnostics}" echo "=== 1. Lokalise API Health ===" API_STATUS=$(curl -sf -o /dev/null -w "%{http_code}" \ "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}" \ -H "X-Api-Token: ${LOKALISE_API_TOKEN}") case...