VAPI•7mo ago

Logic edges in workflows

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

AIEdgeCondition

AIEdgeCondition

AIEdgeCondition and

LogicEdgeCondition

LogicEdgeCondition

LogicEdgeCondition

LogicEdgeCondition, with different syntax.

Now, the issues:

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.
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".
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.

Create Workflow | Vapi

Workflows overview | Vapi

Learn to create robust, deterministic conversation flows with a visual builder.

colossal-harlequinOP•6/11/25, 12:17 PM

Basic workflow with true logic conditions exhibiting behaviour described above in 3. point: be5a4b97-611b-407a-acb0-2ab8cc6405bbbe5a4b97-611b-407a-acb0-2ab8cc6405bb

colossal-harlequinOP•6/11/25, 12:19 PM

Call logs seem to still assume that condition is not logic, but an AI one:

[WARN] [Workflow] AI edge not met. Error: No condition satisfied

[WARN] [Workflow] AI edge not met. Error: No condition satisfied

And start doing a random flow to global node.

VapiAPP•6/12/25, 2:42 AM

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.

dangerous-fuchsia•6/16/25, 1:41 PM

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
```
```
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, logic conditions should:

Use precise variable syntax like {{ city == "San Francisco" }}{{ 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-2ab8cc6405bbbe5a4b97-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:

Navigate to dashboard.vapi.ai/calls
Locate the call where logic conditions didn't work as expected
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

VAPI Dashboard - Voice AI Management Platform

Build and manage voice AI agents that conduct human-like conversations. Access real-time analytics, configure assistants, and monitor your AI voice applications.

Logic edges in workflows

Issue Validation

Current Status & Next Steps

Required Information for Engineering Team

Similar Threads

Similar Threads

Issue Validation

Current Status & Next Steps

Required Information for Engineering Team

Similar Threads