granola-common-errors
Troubleshoot common Granola errors and issues. Use when experiencing recording problems, sync issues, transcription errors, or integration failures. Trigger with phrases like "granola error", "granola not working", "granola problem", "fix granola", "granola troubleshoot".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- granola-common-errors
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Troubleshoot common Granola errors and issues. Use when experiencing recording problems, sync issues, transcription errors, or integration failures. Trigger with phrases like "granola error", "granola not working", "granola problem", "fix granola", "granola troubleshoot".
- allowed-tools
- Read, Write, Edit, Bash(pgrep:*), Bash(ps:*)
- compatible-with
- claude-code, codex, openclaw
03 SKILL.md 正文
Granola Common Errors
Overview
Diagnose and resolve common Granola issues for uninterrupted meeting capture.
Quick Diagnostics
Check Granola Status
# macOS - Check if Granola is running
pgrep -l Granola
# Check audio devices
system_profiler SPAudioDataType | grep "Default Input"
# Check microphone permissions
tccutil list | grep Granola
Common Errors & Solutions
Audio Issues
Error: "No Audio Captured"
Symptoms: Meeting recorded but transcript is empty Causes & Solutions:
| Cause | Solution |
|---|---|
| Wrong audio input | System Preferences > Sound > Input > Select correct device |
| Microphone muted | Check physical mute button on device |
| Permission denied | Grant microphone access in System Preferences |
| Virtual audio conflict | Disable conflicting audio software |
set -euo pipefail
# Reset audio on macOS
sudo killall coreaudiod
Error: "Poor Transcription Quality"
Symptoms: Many errors in transcript Solutions:
- Use quality microphone or headset
- Reduce background noise
- Speak clearly and at moderate pace
- Position microphone closer
Calendar Sync Issues
Error: "Meeting Not Detected"
Symptoms: Granola doesn't auto-start for scheduled meeting Solutions:
-
Check calendar connection:
- Settings > Integrations > Calendar
- Disconnect and reconnect
-
Verify event visibility:
- Event must be on synced calendar
- You must be an attendee
- Event needs video link
-
Force sync:
- Click sync button in Granola
- Wait 30 seconds
- Check if meeting appears
Error: "Calendar Authentication Failed"
Symptoms: Can't connect Google/Outlook calendar Solutions:
1. Clear browser cache
2. Log out of Google/Microsoft account
3. Log back in
4. Try connecting Granola again
5. Use private/incognito browser window
Processing Issues
Error: "Notes Not Appearing"
Symptoms: Meeting ended but no notes generated Solutions:
| Timeframe | Action |
|---|---|
| < 2 min | Wait - processing takes time |
| 2-5 min | Check internet connection |
| 5-10 min | Restart Granola app |
| > 10 min | Contact support |
Error: "Processing Failed"
Symptoms: Error message after meeting Causes:
- Audio file corrupted
- Meeting too short (< 2 min)
- Server issues
- Storage full
Solutions:
- Check Granola status page
- Verify sufficient disk space
- Try re-uploading if option available
- Contact support with meeting ID
Integration Issues
Error: "Zapier Connection Lost"
Symptoms: Automations not triggering Solutions:
- Open Zapier dashboard
- Find Granola connection
- Click "Reconnect"
- Re-authorize access
- Test Zap manually
Error: "Slack/Notion Sync Failed"
Symptoms: Notes not appearing in connected apps Solutions:
- Check integration status in Settings
- Verify target workspace permissions
- Re-authenticate if expired
- Check target channel/database exists
App Issues
Error: "App Won't Start"
Solutions (macOS):
set -euo pipefail
# Force quit Granola
killall Granola
# Clear preferences (caution: resets settings)
rm -rf ~/Library/Preferences/com.granola.*
rm -rf ~/Library/Application\ Support/Granola
# Reinstall
brew reinstall granola
Solutions (Windows):
1. Task Manager > End Granola process
2. Settings > Apps > Granola > Repair
3. If fails, uninstall and reinstall
Error: "Update Failed"
Solutions:
- Close Granola completely
- Download latest from granola.ai/download
- Install over existing version
- Restart computer if needed
Error Code Reference
| Code | Meaning | Action |
|---|---|---|
| E001 | Authentication failed | Re-login to Granola |
| E002 | Audio capture error | Check microphone |
| E003 | Network error | Check internet |
| E004 | Processing timeout | Retry or contact support |
| E005 | Storage full | Free up disk space |
| E006 | Calendar sync error | Reconnect calendar |
When to Contact Support
- Errors persist after troubleshooting
- Data loss or corruption
- Billing issues
- Feature requests
Support: help@granola.ai
Resources
Next Steps
Proceed to granola-debug-bundle for creating diagnostic reports.
Prerequisites
- Access to the Granola Common Errors environment or API
- Required CLI tools installed and authenticated
- Familiarity with Granola Common Errors concepts and terminology
Instructions
- Assess the current state of the Granola Common Errors configuration
- Identify the specific requirements and constraints
- Apply the recommended patterns from this skill
- Validate the changes against expected behavior
- Document the configuration for team reference
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
Error Handling
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Granola Common Errors |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Examples
Basic usage: Apply granola common errors to a standard project setup with default configuration options.
Advanced scenario: Customize granola common errors for production environments with multiple constraints and team-specific requirements.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.