apple-notes-incident-runbook

# Apple Notes Incident Runbook ## Overview This runbook covers the most common Apple Notes automation failures and their resolution procedures. Unlike cloud SaaS incidents that involve API endpoints and status pages, Apple Notes incidents are local to the macOS machine: app crashes, TCC permission revocations, iCloud sync failures, and database corruption. Each incident section follows a detect-diagnose-fix-verify structure. Keep this runbook accessible on any machine running Notes automation. ## Severity Levels | Severity | Description | Example | Response Time | |----------|-------------|---------|---------------| | P1 | All automation blocked | TCC permissions revoked, Notes.app won't launch | Immediate | | P2 | Data inconsistency | iCloud sync stuck, notes missing | Within 1 hour | | P3 | Degraded performance | Slow operations, intermittent timeouts | Within 4 hours | | P4 | Cosmetic/minor | Log warnings, non-critical script errors | Next business day | ## Incident 1: Notes.app Crash During Automation ```bash # DETECT: Check if Notes is running pgrep -x Notes > /dev/null && echo "Notes: running" || echo "Notes: NOT RUNNING" # DIAGNOSE: Check crash logs ls -lt ~/Library/Logs/DiagnosticReports/Notes* 2>/dev/null | head -3 # FIX: Restart Notes with stabilization delay killall Notes 2>/dev/null sleep 3 open -a Notes sleep 5 # Wait for full launch and iCloud handshake # VERIFY: Confirm access is restored osascript -l JavaScript -e 'Application("Notes").defaultAccount...