lindy-common-errors

Lindy Common Errors

Overview

Troubleshooting guide for Lindy AI agent errors. Lindy agents fail at specific points in the workflow: trigger reception, action execution, condition evaluation, or exit condition evaluation. This guide covers each failure class.

Prerequisites

• Access to Lindy dashboard (https://app.lindy.ai)
• Ability to view agent Tasks tab for error details
• For webhook debugging: curl installed

Trigger Errors

Webhook Not Firing

Symptoms: No task created when webhook is sent Causes & Solutions:

# Diagnostic: Test webhook connectivity
curl -v -X POST "https://public.lindy.ai/api/v1/webhooks/YOUR_ID" \
  -H "Authorization: Bearer YOUR_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"test": true}'
# Expect: 200 OK

Email Trigger Not Activating

Symptoms: Emails arrive but agent does not wake up Solutions:

1. Verify Gmail/Outlook authorization is current (re-authorize if expired)
2. Check label filter — Lindy Email Received trigger can filter by label
3. Confirm email matches trigger filter conditions (sender, subject, etc.)
4. Check that agent is active, not paused

Schedule Trigger Missed

Symptoms: Agent did not run at scheduled time Solutions:

1. Verify timezone settings match your expectation
2. Check credit balance — agents stop if credits exhausted
3. Review schedule configuration (daily vs weekday vs custom)

Action Errors

Slack Send Failed

Gmail Send Failed

HTTP Request Action Failed

# Diagnostic: Test target API independently
curl -v -X POST "https://api.yourapp.com/endpoint" \
  -H "Content-Type: application/json" \
  -d '{"test": true}'

Run Code Action Failed

Knowledge Base Returns No Results

Agent Step Errors

Agent Loops Indefinitely

Cause: Exit conditions never satisfied Fix: Add measurable, achievable exit conditions:

Primary: "Found at least 3 relevant results"
Fallback: "Made 5 search attempts without finding results"

Agent Picks Wrong Condition Branch

Cause: Ambiguous condition prompt Fix: Make conditions mutually exclusive with clear criteria:

Branch A: "Go down this path if the email mentions billing, payment, or invoice"
Branch B: "Go down this path if the email mentions a technical issue, bug, or error"
Branch C: "Go down this path for all other topics"

Credit Overrun Warning

Symptom: "Task using more resources than expected" pause Cause: Agent step consuming too many credits (complex reasoning) Fix: Simplify prompt, reduce available skills (2-4 max), use smaller model

Debugging Checklist

1. Open agent Tasks tab — find the failed task
2. Click into the task — review each step's input/output
3. Identify the failing step (red indicator)
4. Check the step's error message and stack trace
5. Verify integration authorizations are current
6. Test the trigger independently (curl for webhooks)
7. Test the action independently (manual run)
8. Check credit balance — insufficient credits halt execution

Error Handling

Resources

• Lindy Documentation
• Lindy Community
• Lindy Status

Next Steps

Proceed to lindy-debug-bundle for comprehensive diagnostics.