granola-incident-runbook

# Granola Incident Runbook

## Overview
Standard operating procedures for responding to Granola incidents and meeting capture failures.

## Incident Severity Levels

| Level | Description | Response Time | Examples |
|-------|-------------|---------------|----------|
| P1 | Critical | < 15 min | Complete outage, data loss |
| P2 | High | < 1 hour | Recording failures, sync issues |
| P3 | Medium | < 4 hours | Single user issues, slow processing |
| P4 | Low | < 24 hours | UI bugs, minor inconveniences |

## Incident Response Flow

```
Incident Detected
       ↓
Assess Severity (5 min)
       ↓
Check Status Page (1 min)
       ↓
┌──────────────────────┐
│ Granola Issue?       │
├──────────────────────┤
│ Yes → Workaround     │
│ No  → Local Debug    │
└──────────────────────┘
       ↓
Communicate Status
       ↓
Track to Resolution
       ↓
Post-Incident Review
```

## Quick Status Check

### Step 1: Check Granola Status
```bash
# Check status page
curl -s https://status.granola.ai/api/v2/status.json | jq '.status'

# Or visit: https://status.granola.ai
```

### Step 2: Test Local Connectivity
```bash
# Test API connectivity
curl -I https://api.granola.ai/health

# Expected: HTTP 200 OK
```

### Step 3: Check Local App Status
```bash
# macOS - Check if Granola is running
pgrep -l Granola

# Check Granola logs
tail -f ~/Library/Logs/Granola/granola.log
```

## Incident: Recording Not Starting

### Symptoms
- Meeting starts but Granola doesn't record
- No recording indicator visible
- Calendar event not detected

### Immediate Actions
```markdown
## Quick Fix (< 5 min)

1. [ ] Manually click "Start Recording" in Granola
2. [ ] Check calendar is connected (Settings > Integrations)
3. [ ] Verify meeting is on synced calendar
4. [ ] Restart Granola app
5. [ ] Check audio permissions granted
```

### Root Cause Investigation
```markdown
## Investigate (if quick fix fails)

1. Calendar Sync Issue:
   - Last sync time?
   - OAuth token valid?
   - Correct calendar selected?