clickup-incident-runbook

# ClickUp Incident Runbook ## Overview Rapid incident response for ClickUp API v2 integration failures. Covers triage, diagnosis by error type, mitigation, and postmortem. ## Severity Classification | Level | Definition | Response Time | Example | |-------|-----------|---------------|---------| | P1 | All ClickUp API calls failing | < 15 min | 401 on all requests, API unreachable | | P2 | Degraded service | < 1 hour | High latency, rate limited, partial 500s | | P3 | Minor impact | < 4 hours | Webhook delays, non-critical endpoint errors | | P4 | No user impact | Next business day | Monitoring gaps, documentation issues | ## Step 1: Quick Triage (< 2 minutes) ```bash #!/bin/bash echo "=== ClickUp Incident Triage ===" # 1. Is ClickUp itself down? echo -n "ClickUp platform: " curl -sf https://status.clickup.com/api/v2/summary.json 2>/dev/null | \ python3 -c "import sys,json; print(json.load(sys.stdin)['status']['description'])" 2>/dev/null \ || echo "UNREACHABLE" # 2. Can we authenticate? echo -n "Auth: " STATUS=$(curl -sf -o /dev/null -w "%{http_code}" \ https://api.clickup.com/api/v2/user \ -H "Authorization: $CLICKUP_API_TOKEN" 2>/dev/null) echo "HTTP $STATUS" # 3. Rate limit status echo -n "Rate limit: " curl -sD - -o /dev/null https://api.clickup.com/api/v2/user \ -H "Authorization: $CLICKUP_API_TOKEN" 2>&1 | \ grep -i "X-RateLimit-Remaining" | awk '{print $2}' | tr -d '\r' # 4. API latency echo -n "Latency: " curl -sf -o /dev/null -w "%{time_total}s\...