Need Help Debugging Unexpected Workflow Errors with Lindy

·Jun 18, 2025 01:47 AM·

Better debugging. I have been stuck the better part of 6 hours trying to debug an issue that came about out of the blue, e.g. no changes were made to the affected workflow. It would be great if I could prompt Lindy to identify the root error cause, and receive notes about what might be causing the problem. Again, this error came about without changes made to the workflow, so I'm guessing that something in Lindy backend has possibly changed.

8 comments

· Sorted by Oldest

Eric
·
·
hey Ronnie P. I experienced this same error today and the issue lay in how the workflow was triggered. I was using two triggers. One was a Talk with other Lindy (which I referenced in a subsequent action) and the other trigger was Chat with this Lindy. When I triggered using Chat with this Lindy it gave me the error you received. If you also have two triggers, it could be a similar cause
Ronnie P.
·
·
I will take a look at this. Unfortunately, I need both triggers in my workflow.
Eric
·
·
If it's the same as mine, I was referencing in a future action something from the Talk with other Lindy trigger. When I triggered using the Chat with this Lindy it didn't have access (no source block) to use in the action. You might just need to change what the actions are referencing rather than reduce your triggers.
Ronnie P.
·
·
Eric I finally identified the issue. It seems that the LLM Call action is no longer working with explicit variables defined by Talk with other Lindy OUTPUT. I replaced the explicit reference with a prompt and things started working again. Very strange...
Ronnie P.
·
·
Eric rolling that comment back 🔝 . This is still not working. Argh.
Marvin A.
·
·
Yeah slight difference for Ronnie P. here. He was referencing the output of the other agent -> identified a bug 👀 Eric was referencing the manual Message Received -> not a bug 🙂 Should be resolved soon! 🙏🏾
👀1
Marvin A.
·
·
This is fixed! ✅🙏🏾
Ronnie P.
·
·
Checking it now.