Hey, it seems that "logic" edges do not work in Workflows and also are not documented properly. Documentation regarding them is found here: https://docs.vapi.ai/workflows/overview#logical-conditions and suggests that you can define logic directly on edge condition, in double curly braces. However in API Reference (https://docs.vapi.ai/api-reference/workflow/workflow-controller-create) there are distinct types of edges:

AIEdgeCondition

and

LogicEdgeCondition

, with different syntax. Now, the issues: 1. By following the documentation and trying to use curly brace syntax in the dashboard does not create a logic condition but an AI one, with a prompt containing that condition - up to an LLM to interpret. 2. If I create a true logic condition using an API, dashboard UI does not display it properly (see screenshot below) and crashes if I try to "Add condition". 3. True logic conditions created via the API never work for me. If I have global node, it gets triggered instead of following the condition logic. I believe this is a serious issue and should be addressed in docs and dashboard, as it is currently extremely confusing. https://cdn.discordapp.com/attachments/1382332348024229979/1382332787985612851/image.png?ex=684cbf7b&is=684b6dfb&hm=e24084454493f45879d10c01de175692631412b4881097383877720b72fe3ba5&

Hey Illuminati, this is a confirmation message to let you know that I'm looking into your ticket and will update you shortly with the resolution or something else.

Hi Illuminati, Thank you for the detailed issue report about logic edge conditions in Workflows. I can confirm that your expectations are absolutely correct and this is indeed a significant issue that needs to be addressed. ## Issue Validation You've identified a real discrepancy between: - **API Reference**: Shows distinct

LogicEdgeCondition

type with specific structure - **Dashboard behavior**: Treats curly brace syntax as AI conditions instead of logic conditions - **Functional reality**: Logic conditions created via API don't work as expected ## Why Your Expectations Are Correct According to the [Vapi Workflows documentation](https://docs.vapi.ai/workflows/overview), logic conditions should: - Use precise variable syntax like

{{ city == "San Francisco" }}

- Provide deterministic, programmatic evaluation - Work reliably for conditional workflow routing The fact that the dashboard crashes when displaying API-created logic conditions and that the system falls back to global nodes indicates a fundamental integration issue between the frontend and backend systems. ## Current Status & Next Steps Our engineering team is actively working on resolving this issue. The problem involves alignment between dashboard condition creation, API processing, and workflow execution logic. ## Required Information for Engineering Team To help our team reproduce and fix this issue quickly, we need: **Call ID**: From your test workflow

be5a4b97-611b-407a-acb0-2ab8cc6405bb

**Specific Call ID**: Please provide the Call ID from a specific test call where logic conditions failed You can find your Call ID by: 1. Navigate to [dashboard.vapi.ai/calls](https://dashboard.vapi.ai/calls) 2. Locate the call where logic conditions didn't work as expected 3. Copy the Call ID from the call details Additional helpful details: - **Timestamp**: When in the call the logic condition should have triggered - **Expected behavior**: Which node the workflow should have routed to - **Actual behavior**: What happened instead (global node trigger, etc.) ## Meanwhile While we work on the fix, as a temporary workaround: - Use AI-based conditions for complex routing logic - Keep logic conditions simple until the issue is resolved - Test via dashboard for logic condition validation