Granola Incident Runbook
Contents
Overview
Standard operating procedures for responding to Granola incidents and meeting capture failures, from recording issues to complete outages.
Prerequisites
- Granola admin access
- Knowledge of incident severity levels
- Communication channels identified
Severity Levels
| Level |
Description |
Response Time |
Example |
| P1 |
Critical |
< 15 min |
Complete outage, data loss |
| P2 |
High |
< 1 hour |
Recording failures, sync issues |
| P3 |
Medium |
< 4 hours |
Single user issues |
| P4 |
Low |
< 24 hours |
UI bugs |
Instructions
Step 1: Assess Severity
Check status page (status.granola.ai), determine scope (single user vs org-wide), classify severity.
Step 2: Quick Fix by Incident Type
- Not Recording: Click Start Recording, check calendar/audio permissions, restart app
- No Audio: Check input device, test mic, restart app
- Processing Stuck: Wait 15 min, check connectivity, restart app
- Integration Failure: Reconnect integration, check destination permissions
- Complete Outage: Enable backup note-taking, monitor status page
Step 3: Communicate Status
Post to internal Slack with status, impact, workaround, and ETA. Update every 30 minutes.
Step 4: Escalate if Needed
IT Support -> Granola Admin -> Team Lead -> VP/CTO (P1 only).
Step 5: Post-Incident Review
Document timeline, root cause, resolution, and prevention steps.
See detailed implementation for status check commands, detailed troubleshooting per incident type, communication templates, and post-incident report template.
Output
- Incident classified and acknowledged
- Quick fix applied or workaround enabled
- Stakeholders notified with status updates
- Post-incident review documented
Error Handling
| Error |
Cause |
Solution |
| Recording not starting |
Calendar not synced |
Reconnect calendar OAuth |
| Empty transcript |
Mic not detected |
Check System Preferences audio input |
| Notes not appearing |
Processing queue delay |
Wait 15 min, check status page |
| Integration broken |
Token expired |
Reconnect in Settings > Integrations |
Examples
Quick Status Check
set -euo pipefail
curl -s https://status.granola.ai/api/v2/status.json | jq '.status'
Resources
Next Steps
Proceed to granola-data-handling for data management procedures.
1---2name: granola-incident-runbook3description: |4 Manage incident response for Granola meeting capture issues.5 Use when handling meeting capture failures, system outages,6 or urgent troubleshooting situations.7 Trigger with phrases like "granola incident", "granola outage",8 "granola emergency", "granola not recording", "granola down".9allowed-tools: Read, Write, Edit, Bash(curl:*)10version: 1.0.011license: MIT12author: Jeremy Longshore <jeremy@intentsolutions.io>13compatible-with: claude-code, codex, openclaw14metadata:15 source: https://skillmd.com/skills/micsapp/granola-incident-runbook16---1718# Granola Incident Runbook1920## Contents21- [Overview](#overview)22- [Prerequisites](#prerequisites)23- [Instructions](#instructions)24- [Output](#output)25- [Error Handling](#error-handling)26- [Examples](#examples)27- [Resources](#resources)2829## Overview30Standard operating procedures for responding to Granola incidents and meeting capture failures, from recording issues to complete outages.3132## Prerequisites33- Granola admin access34- Knowledge of incident severity levels35- Communication channels identified3637## Severity Levels3839| Level | Description | Response Time | Example |40|-------|-------------|---------------|---------|41| P1 | Critical | < 15 min | Complete outage, data loss |42| P2 | High | < 1 hour | Recording failures, sync issues |43| P3 | Medium | < 4 hours | Single user issues |44| P4 | Low | < 24 hours | UI bugs |4546## Instructions4748### Step 1: Assess Severity49Check status page (`status.granola.ai`), determine scope (single user vs org-wide), classify severity.5051### Step 2: Quick Fix by Incident Type52- **Not Recording**: Click Start Recording, check calendar/audio permissions, restart app53- **No Audio**: Check input device, test mic, restart app54- **Processing Stuck**: Wait 15 min, check connectivity, restart app55- **Integration Failure**: Reconnect integration, check destination permissions56- **Complete Outage**: Enable backup note-taking, monitor status page5758### Step 3: Communicate Status59Post to internal Slack with status, impact, workaround, and ETA. Update every 30 minutes.6061### Step 4: Escalate if Needed62IT Support -> Granola Admin -> Team Lead -> VP/CTO (P1 only).6364### Step 5: Post-Incident Review65Document timeline, root cause, resolution, and prevention steps.6667See [detailed implementation](${CLAUDE_SKILL_DIR}/references/implementation.md) for status check commands, detailed troubleshooting per incident type, communication templates, and post-incident report template.6869## Output70- Incident classified and acknowledged71- Quick fix applied or workaround enabled72- Stakeholders notified with status updates73- Post-incident review documented7475## Error Handling76| Error | Cause | Solution |77|-------|-------|----------|78| Recording not starting | Calendar not synced | Reconnect calendar OAuth |79| Empty transcript | Mic not detected | Check System Preferences audio input |80| Notes not appearing | Processing queue delay | Wait 15 min, check status page |81| Integration broken | Token expired | Reconnect in Settings > Integrations |8283## Examples8485### Quick Status Check86```bash87set -euo pipefail88curl -s https://status.granola.ai/api/v2/status.json | jq '.status'89```9091## Resources92- [Granola Status](https://status.granola.ai)93- [Support Center](https://granola.ai/help)94- [Known Issues](https://granola.ai/updates)9596## Next Steps97Proceed to `granola-data-handling` for data management procedures.