Skip to content
lindy-incident-runbook logo

Lindy Incident Runbook

lindy-incident-runbook

Incident response procedures for Lindy AI agent failures and outages.

SKILL.md

Full skill instructions

Lindy Incident Runbook

Overview

Incident response procedures for Lindy AI agent failures. Covers platform outages, individual agent failures, integration breakdowns, credit exhaustion, and webhook endpoint failures.

Incident Severity Levels

SeverityDescriptionResponse TimeExamples
SEV1All agents failing, customer impact15 minutesLindy platform outage, all webhooks failing
SEV2Critical agent down30 minutesSupport bot offline, phone agent unreachable
SEV3Degraded performance2 hoursHigh latency, intermittent failures
SEV4Minor issue24 hoursNon-critical agent misconfigured

Quick Diagnostics (First 5 Minutes)

Step 1: Check Lindy Platform Status

# Is Lindy up?
curl -s -o /​dev/​null -w "Lindy API: HTTP %{http_code}\n" \
  "https://public.lindy.ai" --max-time 5

# Check status page
echo "Status page: https://status.lindy.ai"

Step 2: Check Your Integration

# Is your webhook receiver up?
curl -s -o /​dev/​null -w "Our endpoint: HTTP %{http_code}\n" \
  "https://api.yourapp.com/​health" --max-time 5

# Is the webhook auth working?
curl -s -o /​dev/​null -w "Webhook auth: HTTP %{http_code}\n" \
  -X POST "https://api.yourapp.com/​lindy/​callback" \
  -H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
  -H "Content-Type: application/​json" \
  -d '{"test": true}' --max-time 5

Step 3: Check Credit Balance

Log in at > Settings > Billing

  • Credits at 0? Agents stop processing
  • Credits low? Non-essential agents may be paused

Incident Playbooks

Incident: Lindy Platform Outage (SEV1)

Symptoms: All agents failing, status.lindy.ai shows incident Impact: All Lindy-dependent workflows halted

Runbook:

  1. Confirm outage at https://status.lindy.ai
  2. Notify team: "Lindy platform outage confirmed. All agents affected."
  3. Activate fallback procedures:
    • Route support emails to human inbox
    • Disable webhook triggers from your app
    • Queue events for replay when Lindy recovers
  4. Monitor status page for recovery
  5. When recovered: re-enable triggers, replay queued events, verify agent health

Fallback code:

async function triggerLindyWithFallback(payload: any) {
  try {
    const response = await fetch(WEBHOOK_URL, {
      method: 'POST',
      headers: {
        'Authorization': `Bearer ${SECRET}`,
        'Content-Type': 'application/​json',
      },
      body: JSON.stringify(payload),
      signal: AbortSignal.timeout(10000), // 10s timeout
    });

    if (!response.ok) throw new Error(`HTTP ${response.status}`);
    return { routed: 'lindy' };
  } catch (error) {
    console.error('Lindy unreachable, activating fallback:', error);
    await queueForReplay(payload); // Store for later
    await notifyTeam(`Lindy trigger failed: ${error}`);
    return { routed: 'fallback' };
  }
}

Incident: Individual Agent Failure (SEV2)

Symptoms: Specific agent tasks showing "Failed" status Impact: One workflow affected, others may be fine

Runbook:

  1. Open agent > Tasks tab > Filter by "Failed"
  2. Click latest failed task — identify the failing step
  3. Diagnose based on failing step type:
    • Trigger step: Auth expired? Filter too restrictive?
    • Action step: Integration token expired? Target API down?
    • Condition step: Ambiguous condition prompt?
    • Agent step: Looping? Exit conditions unreachable?
  4. Fix the root cause:
    • Re-authorize expired integrations
    • Fix action configuration
    • Simplify condition prompts
    • Add fallback exit conditions
  5. Test with a manual trigger
  6. Monitor next 5 tasks for success

Incident: Integration Auth Expired (SEV2-3)

Symptoms: Actions failing with "Not authorized" or "Token expired" Impact: All tasks using that integration fail

Runbook:

  1. Identify which integration is failing (Gmail, Slack, Sheets, etc.)
  2. In Lindy dashboard: Settings > Integrations
  3. Find the expired connection (may show warning icon)
  4. Click Re-authorize and complete OAuth flow
  5. Re-test the agent with a manual trigger
  6. Set calendar reminder for 90-day re-authorization check

Incident: Credit Exhaustion (SEV2-3)

Symptoms: Agents stop running, no new tasks created Impact: All agents paused until credits refill

Runbook:

  1. Confirm at Settings > Billing: credits at 0
  2. Immediate: Upgrade plan or purchase additional credits
  3. Investigate: Which agent consumed the most credits?
  4. Root cause: trigger storm? looping agent step? large model overuse?
  5. Fix: Add trigger filters, set exit conditions, downgrade model
  6. Prevent: Set budget alerts at 50%, 80%, 95% thresholds

Incident: Webhook Endpoint Failure (SEV2-3)

Symptoms: Lindy agent runs but your callback never receives data Impact: Agent completes but results are lost

Runbook:

  1. Check your endpoint health: curl -s https://api.yourapp.com/​health
  2. Check server logs for incoming requests from Lindy
  3. Verify the HTTP Request action URL matches your production endpoint
  4. Test endpoint independently: send a POST with curl
  5. If endpoint was down: replay failed tasks (re-trigger the agent)
  6. If URL mismatch: update URL in Lindy agent HTTP Request action

Escalation Matrix

LevelContactWhen
L1On-call engineerInitial response, diagnostics
L2Engineering leadAfter 30 min SEV1, 1 hour SEV2
L3VP EngineeringAfter 1 hour SEV1
Lindy Support[email protected]Confirmed Lindy platform issue

Post-Incident Template

## Incident Report

**Date**: YYYY-MM-DD
**Severity**: SEV[1-4]
**Duration**: [start time] to [end time] ([total minutes])
**Impact**: [what was affected, customer impact]

### Timeline
- HH:MM — Issue detected via [monitoring/​user report]
- HH:MM — On-call paged, diagnostics started
- HH:MM — Root cause identified: [cause]
- HH:MM — Fix applied: [what was done]
- HH:MM — Service restored, monitoring confirmed

### Root Cause
[Technical description of what failed and why]

### Resolution
[What was done to fix it]

### Prevention
- [ ] [Action item 1]
- [ ] [Action item 2]
- [ ] [Action item 3]

Error Handling

Incident TypeDetectionAutomated Response
Platform outageHealth check failsQueue events, notify team
Agent failureTask Completed triggerSlack alert to #ops
Auth expiryAction step failsAlert + re-auth link
Credit exhaustionBilling checkPause non-critical agents
Endpoint downHealth checkRedirect to fallback

Resources

Next Steps

Proceed to lindy-data-handling for data security and compliance.

More skills from jeremylongshore

openrouter-compliance-review logo
jeremylongshore/claude-code-plugins-plus-skills

openrouter-compliance-review

Review OpenRouter integration for regulatory compliance (SOC2, GDPR,

2.8K 0
View
maintainx-data-handling logo
jeremylongshore/claude-code-plugins-plus-skills

maintainx-data-handling

Data synchronization, ETL patterns, and data management for MaintainX.

2.8K 0
View
groq-core-workflow-a logo
jeremylongshore/claude-code-plugins-plus-skills

groq-core-workflow-a

Execute Groq primary workflow: chat completions with tool use and JSON

2.8K 0
View
validating-csrf-protection logo
jeremylongshore/claude-code-plugins-plus-skills

validating-csrf-protection

Validate CSRF protection implementations for security gaps. Use when

2.8K 0
View
api-contract logo
jeremylongshore/claude-code-plugins-plus-skills

api-contract

Configure this skill should be used when the user asks about "API contract",

2.8K 0
View
ideogram-incident-runbook logo
jeremylongshore/claude-code-plugins-plus-skills

ideogram-incident-runbook

Execute Ideogram incident response with triage, mitigation, and postmortem.

2.8K 0
View
gamma-sdk-patterns logo
jeremylongshore/claude-code-plugins-plus-skills

gamma-sdk-patterns

Reusable patterns for the Gamma REST API (no SDK exists).

2.8K 0
View
deepgram-sdk-patterns logo
jeremylongshore/claude-code-plugins-plus-skills

deepgram-sdk-patterns

Apply production-ready Deepgram SDK patterns for TypeScript and Python.

2.8K 0
View
openrouter-upgrade-migration logo
jeremylongshore/claude-code-plugins-plus-skills

openrouter-upgrade-migration

Migrate to OpenRouter from direct provider APIs or upgrade between SDK/model

2.8K 0
View
openrouter-common-errors logo
jeremylongshore/claude-code-plugins-plus-skills

openrouter-common-errors

Diagnose and fix common OpenRouter API errors. Use when encountering

2.8K 0
View
linear-cost-tuning logo
jeremylongshore/claude-code-plugins-plus-skills

linear-cost-tuning

Optimize Linear API usage, reduce unnecessary calls, and maximize

2.8K 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View