micsapp Lokalise Incident Runbook
Overview
Rapid incident response procedures for Lokalise-related outages and issues.
Prerequisites
- Access to Lokalise dashboard and status page
- Application logs and monitoring dashboards
- Communication channels (Slack, PagerDuty)
- Rollback procedures documented
Instructions
- Severity Levels
- Quick Triage Commands
- Decision Tree
- Immediate Actions by Error Type
- Communication Templates
- Post-Incident
- Rollback Procedures
For full implementation details, load: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Output
- Issue identified and categorized
- Remediation applied
- Stakeholders notified
- Evidence collected for postmortem
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Can't reach status page | Network issue | Use mobile or VPN |
| Logs unavailable | Logging down | Check logging service |
| Fallback not working | Not configured | Enable static fallback |
| Token rotation fails | Permission denied | Escalate to admin |
Examples
One-Line Health Check
set -euo pipefail
curl -sf https://your-app.com/health/lokalise | jq '.status' || echo "UNHEALTHY"
Quick Fallback Enable
// Emergency fallback - use in incident
process.env.LOKALISE_FALLBACK_ENABLED = "true";
// Your translation loader should check this
const useFallback = process.env.LOKALISE_FALLBACK_ENABLED === "true";
if (useFallback) {
return loadBundledTranslations(locale);
}
Resources
Next Steps
For data handling, see lokalise-data-handling.