grammarly-incident-runbook

# Grammarly Incident Runbook ## Overview Incident response procedures for Grammarly writing API integration failures. Covers text check timeouts, suggestion quality degradation, OAuth token failures, and rate limit storms. Grammarly powers real-time writing assistance, so API incidents directly impact user-facing text checking, scoring workflows, and content quality pipelines. Classify severity immediately using the matrix below and follow the corresponding playbook. ## Severity Levels | Level | Definition | Response Time | Example | |-------|-----------|---------------|---------| | P1 - Critical | Full API outage, all scoring requests fail | 15 min | 5xx on `/v2/scores` for all requests | | P2 - High | OAuth token failures or sustained timeouts | 30 min | All authenticated requests return 401 | | P3 - Medium | Rate limit storms or elevated latency | 2 hours | 429 responses, scoring takes 10s+ per request | | P4 - Low | Suggestion quality drift or single endpoint issue | 8 hours | Scores returning but correctness values seem off | ## Diagnostic Steps ```bash # Test API health (unauthenticated) curl -s -o /dev/null -w "HTTP %{http_code}\n" \ https://api.grammarly.com/ecosystem/api/v2/scores # Test authenticated scoring curl -s -w "\nHTTP %{http_code}\n" \ -H "Authorization: Bearer $GRAMMARLY_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -X POST https://api.grammarly.com/ecosystem/api/v2/scores \ -d '{"text": "Test sentence for Grammarly API diagnostic ...