I have this problem too. It cannot go to next step with simple answer like yes or no. The id is d0840bce-e3c2-4cff-b4f3-09435de5fa68. Can you please help?

Hi there! 👋 I understand your frustration with the Workflow gather feature not proceeding after yes/no answers. This appears to be a known issue in Vapi. Users have reported that conditions in workflows don't function correctly after a Gather step when responding with yes or no - the workflow doesn't proceed and may show an error without details [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1342196090128306246). Another user documented a similar problem where an assistant asks a question like "Do you have medicare parts A & B?" and despite a "Yes" response, the system outputs an error and doesn't continue [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1342196090128306246). While I don't have specific information about your particular workflow configuration, here are some things to check: 1. Verify that your Gather task is correctly configured with the proper data type (boolean) for yes/no answers 2. Check any conditional logic that might be causing issues 3. Consider recording a video of the issue to share with Vapi support The Vapi team is aware of these types of issues and is investigating them. Sharing your workflow ID (which you've already provided) and multimedia evidence can help them identify the cause more quickly. Sources: - [Discord Channel User Reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342196090128306246) - [Discord Channel Conditional Logic Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334666797932089405) - [Vapi Documentation Gather Task](https://docs.vapi.ai/workflows/tasks/gather)

I have shared the workflow id. thanks

I can see the problem in your workflow. The issue is in the conditional logic that's preventing "yes" or "no" answers from properly progressing to the next step. ## The Problem Identified Looking at your workflow configuration, I notice a mismatch between how the data is collected and how it's being evaluated in the conditions: 1. In your gather_1741245344439 node, you're correctly collecting a boolean value:

json
   "has_time": {
     "type": "boolean",
     "description": "Whether the caller has time for a review. yes=true, no=false..."
   }

2. However, in your conditional edges, you're comparing this boolean to strings:

json
   "condition": {
     "type": "logic",
     "liquid": "{% if has_time == Yes %} true {% endif %}"
   }

3. And similarly for "No":

json
   "condition": {
     "type": "logic",
     "liquid": "{% if has_time == No %} true {% endif %}"
   }

This is causing the conditions to fail because you're comparing a boolean value (`true`/`false`) with string literals (`"Yes"`/`"No"`), which don't match. ## The Solution You need to modify the Liquid template conditions in your workflow to compare with boolean values instead: 1. Change {% if has_time == Yes %} to {% if has_time == true %} or simply {% if has_time %} 2. Change {% if has_time == No %} to {% if has_time == false %} or simply {% if not has_time %} You can make these changes in the Vapi workflow editor for your assistant (ID: d0840bce-e3c2-4cff-b4f3-09435de5fa68). ## Logs Verification From your logs, I can see that the workflow did collect the has_time value as a boolean:

"🔵 07:51:51:581 [Workflow] [gather#gather_1741245344439] Output variable values: {"has_time": true}"

But then it failed when trying to evaluate the conditions because it was looking for string values that didn't match the boolean. This simple update to your conditional liquid syntax should resolve the issue and allow your workflow to progress normally when users respond with "yes" or "no"