I am currently experiencing an issue while implementing a workflow using the beta version of Vapi.ai. Since the "Gather" node has been deprecated in this version, I am using the "Conversation" node as advised by Vapi.ai support. In my workflow, the initial node is a Conversation node with the following prompt: *"Exactly Say: 'Hi! I am a virtual assistant, talking on behalf of Coaldev. Do you have a moment to talk?' Listen to the user response carefully. Based on their response, set the variable ready_to_talk as follows: Set to true if the user indicates they are available (e.g., 'yes', 'sure', 'I have a minute', 'go ahead'). Set to false if the user says they are not available or busy (e.g., 'no', 'not now', 'I'm in a meeting', 'call later'). Do not force the conversation if the user is not available. Always be polite and respectful."* A boolean variable ready_to_talk is declared in this node to capture this response. Following this node, the workflow branches into two separate paths: One for when ready_to_talk is true One for when ready_to_talk is false Issue: The workflow is not proceeding according to the value of the ready_to_talk variable. Regardless of the user's response, the conditional branching does not seem to be functioning as expected. I am unable to determine whether the issue lies in how the variable is being set, evaluated, or passed between nodes. I would appreciate any insights or guidance on ensuring the conditional branching works correctly based on the ready_to_talk variable in the Conversation node. https://cdn.discordapp.com/attachments/1374825746648006857/1374825746819846224/image.png?ex=682f75c1&is=682e2441&hm=f78fe5a397eb032eda95d76f81e5ab3c83e4653229422fad20f59c9b0f780097&

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!