Lindy Incident Runbook

Overview

Incident response procedures for Lindy AI integration issues.

Prerequisites

• Access to Lindy dashboard
• Monitoring dashboards available
• Escalation contacts known
• Admin access to production

Incident Severity Levels

For detailed implementation code and configurations, load the reference guide: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)

Quick Diagnostics

Step 1: Check Lindy Status

Step 2: Verify Authentication

Step 3: Check Rate Limits

Common Incidents

Incident: Complete API Outage

Symptoms:

• All API calls failing
• 5xx errors from Lindy

Runbook: Fallback Code:

Incident: Rate Limiting

Symptoms:

• 429 errors
• "Rate limit exceeded" messages

Runbook: Throttling Code:

Incident: Agent Failures

Symptoms:

• Specific agent not responding
• Unexpected outputs
• Timeout errors

Runbook: Diagnostic Script:

Incident: High Latency

Symptoms:

• Response times > 10 seconds
• Timeouts increasing

Runbook:

Escalation Matrix

Post-Incident

Incident Report Template

Output

• Quick diagnostic commands
• Common incident runbooks
• Fallback code patterns
• Escalation procedures
• Post-incident template

Resources

• Lindy Status
• Lindy Support
• API Reference

Next Steps

Proceed to lindy-data-handling for data management.

Instructions

1. Assess the current state of the Lindy Incident Runbook configuration
2. Identify the specific requirements and constraints
3. Apply the recommended patterns from this skill
4. Validate the changes against expected behavior
5. Document the configuration for team reference

Error Handling

Examples

Basic usage: Apply lindy incident runbook to a standard project setup with default configuration options.

Advanced scenario: Customize lindy incident runbook for production environments with multiple constraints and team-specific requirements.