home / skills / jeremylongshore / claude-code-plugins-plus-skills / fireflies-common-errors

This skill helps diagnose and fix Fireflies.ai errors quickly by guiding you through common issues, fixes, and verification steps.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill fireflies-common-errors

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.3 KB
---
name: fireflies-common-errors
description: |
  Diagnose and fix Fireflies.ai common errors and exceptions.
  Use when encountering Fireflies.ai errors, debugging failed requests,
  or troubleshooting integration issues.
  Trigger with phrases like "fireflies error", "fix fireflies",
  "fireflies not working", "debug fireflies".
allowed-tools: Read, Grep, Bash(curl:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Fireflies.ai Common Errors

## Overview
Quick reference for the top 10 most common Fireflies.ai errors and their solutions.

## Prerequisites
- Fireflies.ai SDK installed
- API credentials configured
- Access to error logs

## Instructions

### Step 1: Identify the Error
Check error message and code in your logs or console.

### Step 2: Find Matching Error Below
Match your error to one of the documented cases.

### Step 3: Apply Solution
Follow the solution steps for your specific error.

## Output
- Identified error cause
- Applied fix
- Verified resolution

## Error Handling

### Authentication Failed
**Error Message:**
```
Authentication error: Invalid API key
```

**Cause:** API key is missing, expired, or invalid.

**Solution:**
```bash
# Verify API key is set
echo $FIREFLIES_API_KEY
```

---

### Rate Limit Exceeded
**Error Message:**
```
Rate limit exceeded. Please retry after X seconds.
```

**Cause:** Too many requests in a short period.

**Solution:**
Implement exponential backoff. See `fireflies-rate-limits` skill.

---

### Network Timeout
**Error Message:**
```
Request timeout after 30000ms
```

**Cause:** Network connectivity or server latency issues.

**Solution:**
```typescript
// Increase timeout
const client = new Client({ timeout: 60000 });
```

## Examples

### Quick Diagnostic Commands
```bash
# Check Fireflies.ai status
curl -s https://status.fireflies.com

# Verify API connectivity
curl -I https://api.fireflies.com

# Check local configuration
env | grep FIREFLIES
```

### Escalation Path
1. Collect evidence with `fireflies-debug-bundle`
2. Check Fireflies.ai status page
3. Contact support with request ID

## Resources
- [Fireflies.ai Status Page](https://status.fireflies.com)
- [Fireflies.ai Support](https://docs.fireflies.com/support)
- [Fireflies.ai Error Codes](https://docs.fireflies.com/errors)

## Next Steps
For comprehensive debugging, see `fireflies-debug-bundle`.

Overview

This skill diagnoses and fixes common Fireflies.ai errors and exceptions encountered during integration or automated workflows. It guides you from quick identification to concrete fixes and verification steps. Use it to resolve authentication, rate-limiting, network, and configuration issues rapidly.

How this skill works

The skill inspects error messages, HTTP status codes, and local environment configuration to map issues to documented root causes. It then recommends targeted remediation steps such as verifying API keys, adjusting timeouts, implementing backoff, and collecting diagnostic bundles. Finally, it suggests verification commands and escalation steps to confirm resolution.

When to use it

  • When you see authentication failures or invalid API key errors
  • When requests fail due to rate limits or timeouts
  • When integrations stop syncing or API requests return errors
  • During triage of failed automated workflows or CI jobs
  • Before contacting Fireflies support to collect reproducible evidence

Best practices

  • Store API keys in environment variables and validate them during deployment
  • Implement exponential backoff and retry logic for transient 429/503 responses
  • Increase client timeout for long-running requests and test network latency
  • Collect request IDs, logs, and a debug bundle before escalating to support
  • Run quick status and connectivity checks as part of automated health probes

Example use cases

  • Fixing an "Invalid API key" error by checking env vars and rotating credentials
  • Resolving "Rate limit exceeded" by introducing exponential backoff and queueing bursts
  • Addressing "Request timeout" by increasing client timeout and verifying network routes
  • Running quick diagnostic commands to confirm API reachability and service status
  • Collecting a debug bundle and support-ready evidence for escalations

FAQ

What first step should I take when a Fireflies request fails?

Check the exact error message and request ID in logs, verify environment variables for the API key, and run a quick connectivity check (curl to status and API endpoints).

How do I handle repeated 429 rate limit errors?

Implement exponential backoff with jitter, reduce request concurrency, and cache responses where possible. Monitor rate headers and throttle clients based on returned retry-after values.