| name | lindy-incident-runbook |
| description | Incident response procedures for Lindy AI agent failures and outages.
Use when responding to incidents, troubleshooting agent outages,
or creating on-call procedures for Lindy-powered systems.
Trigger with phrases like "lindy incident", "lindy outage",
"lindy on-call", "lindy runbook", "lindy down".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.15.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","lindy","incident-response"] |
| compatibility | Designed for Claude Code |
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
| Severity | Description | Response Time | Examples |
|---|
| SEV1 | All agents failing, customer impact | 15 minutes | Lindy platform outage, all webhooks failing |
| SEV2 | Critical agent down | 30 minutes | Support bot offline, phone agent unreachable |
| SEV3 | Degraded performance | 2 hours | High latency, intermittent failures |
| SEV4 | Minor issue | 24 hours | Non-critical agent misconfigured |
Quick Diagnostics (First 5 Minutes)
Step 1: Check Lindy Platform Status
curl -s -o /dev/null -w "Lindy API: HTTP %{http_code}\n" \
"https://public.lindy.ai" --max-time 5
echo "Status page: https://status.lindy.ai"
Step 2: Check Your Integration
curl -s -o /dev/null -w "Our endpoint: HTTP %{http_code}\n" \
"https://api.yourapp.com/health" --max-time 5
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)
