granola-incident-runbook

# Granola Incident Runbook ## Overview Standard operating procedures for Granola incidents — from individual recording failures to organization-wide outages. Covers triage, remediation, communication, escalation, and post-incident review. Designed for IT admins, team leads, and individual users. ## Prerequisites - Granola admin access (for org-level incidents) - Bookmark [status.granola.ai](https://status.granola.ai) for service status - Internal communication channel identified (#granola-support or similar) ## Instructions ### Step 1 — Triage: Assess Severity ```bash # Quick status check curl -s "https://status.granola.ai/api/v2/status.json" 2>/dev/null | python3 -c " import json, sys try: data = json.load(sys.stdin) indicator = data.get('status', {}).get('indicator', 'unknown') desc = data.get('status', {}).get('description', 'Unknown') print(f'Status: {indicator} — {desc}') except: print('Cannot reach status page — possible network issue') " || echo "Network error — check internet connection" ``` | Severity | Description | Response Time | Example | |----------|-------------|---------------|---------| | **P1 Critical** | Org-wide outage, data loss risk | Immediate | Granola service down, no one can record | | **P2 High** | Multiple users affected | < 1 hour | Recording fails for a team, sync broken | | **P3 Medium** | Single user issue | < 4 hours | One person's transcription stopped | | **P4 Low** | Minor issue, workaround exists | < 24 hours | UI...