How to Troubleshoot Errors in Lindy Lindy makes automation seamless, but occasional errors can occur. This guide will help you quickly identify, understand, and resolve common issues, so your workflows stay on track.
Why do agents error? Most agent errors come down to simple setup mistakes—missing skills, unclear prompts, or undefined exit conditions. It’s rarely a system issue. Before assuming something’s broken, double-check your configuration—the fix is usually right there.
This guide covers: How to identify an error General troubleshooting steps Common errors and fixes (FAQ) How to report a bug HTTP status codes and their meanings How to identify an error When an error occurs, Lindy notifies you directly within your Task History , Flow Editor , and via email, so you can address issues immediately.
Check the Task History: Go to the Tasks View section. Look for a task marked as Errored . Click on the errored task to see details and suggested fixes. Review Errors in the Flow Editor using Test Mode: Open the workflow in the editor. Enter the “Test Mode” Run your test Lindy will usually tell you where & why it got stuck. In this case - we offer an “Edit action configuration” button that will open up the erroring step.
Additionally, when an error occurs, Lindy emails you with details about the issue and possible troubleshooting steps.
Pro Tip: If an integrated app is down, Lindy will notify you. You can also check the app’s status page for real-time updates.
General Troubleshooting Tips General Troubleshooting Tips Start by reviewing the task: Navigate to the Tasks Panel, select the errored task, and review exactly what Lindy executed before the failure. This is the primary place to identify what went wrong. If available, use the provided button to configure the action step or trigger that failed.Check the error message: Use the Testing Panel to review all messages sent within the workflow. The error message will often indicate what went wrong and how to resolve it.Review triggers and action steps: Ensure all triggers and action steps are set up correctly. Check that the correct inputs, conditions, and dependencies are in place.Monitor outages: If an integrated app is down, Lindy will notify you. You can also check the app’s status page for real-time updates.Review documentation: Visit the Lindy’s Academy for detailed guides and best practices.Common Errors and Fixes (FAQ) “The Input provided is too long” This means the task context is exceeding the allowed limit. To resolve this, follow Lindy’s guide on reducing context size . Key steps include:
Filtering unnecessary high-volume triggers. Using a more cost-efficient language model. Optimizing the workflow to minimize redundant data. “Cannot start test. Cannot find the conversation trigger” This error usually indicates a misconfiguration with triggers. Review Lindy’s guide on triggers to:
Verify trigger setup in the workflow. Ensure event-based triggers have the right conditions. Check if multiple triggers conflict with each other. “My apologies [Name], I'm having trouble completing this task.” This error typically means the agent is unable to complete its assigned task. Here are some possible reasons and fixes:
Missing Exit Condition : If the agent is handling a complex task or using multiple skills, it may not know when to stop.Fix: Define a clear exit condition, so the agent knows when the task is complete.Skills Issue : The agent may lack the necessary skills to finish the task.Fix: Assign the required skills, keeping the total below four skills per agent for most tasks.Prompt Issue : The instructions might be unclear or too vague.Fix: Refine the prompt to ensure the agent fully understands the task. Check out our prompting guide for more information.For a deeper dive into AI agents, exit conditions, and skill assignments, check out Lindy’s guide on AI agents .
“Failed to save the current flow.” This error typically indicates a misconfiguration in the trigger. The error message will provide more details, such as "Invalid trigger authorization" , to help identify the issue.
How to Fix:
Verify that a trigger is set up – Ensure your workflow has an active trigger.Check the trigger configuration – Review settings like authentication, permissions, and required parameters.For more details, refer to Lindy’s guide on triggers .
“My Email received trigger does not fire in test mode” If you email yourself & the sender and recipient email addresses are the same, it won’t trigger the Email Received trigger. This is intentional to prevent infinite loops and other unintended behaviours.
How to Fix: Use a different email address to test the trigger. If you’re testing a Lindy, send the email from a separate account instead of your own. For more details, refer to Lindy’s guide on email responding .
"Task Stopped Due to Insufficient Credits" If a Lindy task stops because of credit limits, it won’t automatically restart. However, you can manually resume it.
How to Fix: Task View , find the incomplete task, and click "Retry" to continue from where it stopped.
If you’re frequently hitting credit limits, consider upgrading your plan. Learn more about how Lindy’s billing and credits work here .
How to Report a Bug If you suspect a bug or need help with Lindy, report it through one of these channels:
Email: Send an email to support@lindy.aiSlack Community: Post in the Lindy Community ⚠️ Make sure to include a task URL! Providing the task URL helps us look directly into the issue, making it easier to diagnose and resolve problems quickly. Please follow these steps to share your Lindy task URL:
Click your Lindy agent → click “Tasks” . Find the task you need help with. Click the specific task (you should see the full execution). Copy that page URL from your browser. Paste the URL in your support request. Note: The URL should include “conversationID” followed by a number.
💡 Screenshots are also helpful!
By following these steps, we can quickly resolve most issues and keep your automations running smoothly.
HTTP Status Codes Lindy interacts with various external services, and sometimes errors come from those connections. Here’s what common HTTP error codes mean:
400 - Bad Request : The request was incorrect—double-check your input data.401 - Unauthorized : Authentication is missing or incorrect.403 - Forbidden : You don’t have permission to access this resource.404 - Not Found : The requested resource doesn’t exist.422 - Unprocessable Entity : Data format is invalid.429 - Too Many Requests : You’ve hit a rate limit—try again later.500 - Internal Server Error : Something went wrong on the external service’s end.Some HTTP errors in Lindy originate from third-party services, meaning the issue is often outside Lindy's control. While some errors can be fixed by adjusting your configuration, others may require checking the third-party provider’s documentation or contacting their support team for further assistance.
Still Stuck? If you’ve checked your configuration and third-party documentation but still need help, ask in the Lindy Community for additional insights or reach out to our support team.
-min.jpg)
