We are experiencing a critical issue where a conversation scoped variable is consistently undefined when passed as an argument to a tool from within a single Autonomous Node. The Workflow (All within one Autonomous Node): Prompt Logic: The node's instructions guide the LLM through a conversation. At one step, the prompt contains this logic: IF the user says "Yes" to the budget question, set the conversation variable 'budget_confirmed' = true., If not then = false Variable Set: We have confirmed through conversation that the LLM successfully understands and sets this budget_confirmed variable. Tool Call: At the end of the prompt, we instruct the LLM to call our send_lead tool and pass the value of the budget_confirmed variable to the tool's budget argument. budget: The value from the 'budget_confirmed' variable. The Problem: The send_lead tool is consistently receiving undefined for the budget argument. It seems the LLM is unable to retrieve the value of the conversation.budget_confirmed variable from its memory at the exact moment it constructs the tool call. Is there a specific syntax or pattern required within an Autonomous Node's prompt to reliably access and pass a conversation scoped variable to a tool? Thank you.

I'm experiencing the same as reported to @loud-crowd-60573 too. Maybe it is related to the latest autonomous node update the team took note of. Hopefully it can be resolved soon

I'm having a similar issue. My prompt tells the autonomous node to parse the user's input and save it to 2-3 variables based on what is in the input, but then those variables are blank when it comes time to use them to search a table.

Can you drop your workspace ID?

wkspace_01K09JY43WBYXTCTFQGTC36C2M

This is indeed a bug, we are waiting for it to be fixded 🫡

Thanks @loud-crowd-60573! The variables are saved correctly now. But there's a new issue This is my Loom video and report ID FYA https://www.loom.com/share/2e6cad0d789d46718b59379b5573e2f9 report_01KD4SWAAPNKF8XA0KMS32Y8HY

keep us posted 🙂