Lindy Agent Fails to Find References on Defined Paths

·

Further testing reveals that the Lindy agent is failing to find references along the defined paths. https://lindycommunity.slack.com/archives/C07GEAA4S04/p1750144456577739

Marvin A.
·
·
this likely is bc you referenced a variable that is not available during this task execution. Are you using multiple triggers? Happy to take a look if you share the task URL!
Ronnie P.
·
·
I will share via DM.
🙏1
Ronnie P.
·
·
One note, Marvin A.. These two Lindy's were working without issue until yesterday. No changes made on my end.
👀1
Ronnie P.
·
·
Further, I can see that Conversation Threads I could previously select are no longer selectable. E.g. They appear in the menu; however, when I click on them nothing happens.
Ronnie P.
·
·
The Select Thread remains empty.
Ronnie P.
·
·
Further investigation, I ran several tests and have confirmed that the Talk to Other Lindy (Agent Message Received) isn't the issue. It seems that the Lindy Utility: Call a Large Language Model (LLM) isn't being correctly referenced downstream, hence the "#" error.
👀1
Marvin A.
·
·
I was able to repro! Flagged this — thanks for reporting, Ronnie! 🙏🏾 Will let you know once it’s fixed.
Ronnie P.
·
·
Marvin A. any thoughts on root cause? Is this a Lindy bug? The workflow was up and running and working great and then stopped working without any changes being made to the workflow components.
Marvin A.
·
·
This is fixed! ✅🙏🏾