granola-incident-runbook

name	granola-incident-runbook
description	Incident response procedures for Granola meeting capture failures and outages. Use when meetings aren't recording, transcription fails mid-meeting, integrations stop syncing, or the Granola service is down. Trigger: "granola incident", "granola outage", "granola down", "granola not recording", "granola emergency".
allowed-tools	Read, Write, Edit, Bash(curl:*), Bash(pgrep:*), Bash(pkill:*), Bash(open:*)
version	1.13.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","granola","incident-response"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

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 for service status
• Internal communication channel identified (#granola-support or similar)

Instructions

Step 1 — Triage: Assess Severity

# 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 glitch, slow processing

Scope assessment questions:

1. Is it just you, or are others affected too? → Ask in #granola-support
2. Is status.granola.ai showing an incident? → P1/P2 if yes
3. Was it working earlier today? → Recent change (OS update, permissions) likely
4. Which platform? (Zoom/Meet/Teams) → Platform-specific audio routing

Step 2 — Remediation by Incident Type

---

Incident: "Meeting Not Recording"

P3 (single user) or P2 (team-wide)