Debug Mode
> See exactly which path your flow took and what values each node received and produced.
Debug Mode gives you a visual trace of your flow execution directly on the Builder canvas. You can see which sequence connections were followed, what data each node received, and how long each node took to run.
Activating debug mode
1. Expand the Console at the bottom of the Builder. 2. Click the Debug button in the terminal panel. 3. Click Test to run your route. 4. Watch the canvas update in real time as the flow executes.
Debug mode only works on dev routes (the version you are editing in the Builder).
Execution path highlighting
When a test runs with debug mode enabled, the Builder canvas shows which connections were followed:
- Executed connections turn orange, showing the exact path through your flow.
- Unexecuted connections keep their default color.
This makes it easy to see which branches were taken in If/Switch nodes and where execution stopped.
Node values
After execution, each node that ran shows overlay boxes with its data:
Input values
An Inputs overlay appears on each executed node, showing every value that was passed into the node. For example, on an HTTP Request node you might see the URL, method, and headers that were used.
Output values
An Outputs overlay shows what the node produced. For example, on an HTTP Request node you would see the response body, status code, and status text.
JSON values are expandable so you can inspect nested objects and arrays.
Execution time
A small time badge appears on each node showing how many milliseconds it took to execute. This helps you identify slow nodes in your flow.
Using debug mode effectively
Finding errors
If a flow returns an unexpected result:
1. Enable Debug Mode and run the test. 2. Follow the orange path to see which nodes executed. 3. Check the Outputs overlay on each node to find where the data went wrong. 4. Look for nodes that did not execute (no orange connections leading to them) -- this often means a condition evaluated differently than expected.
Performance profiling
Check the execution time badges to find slow nodes. Common causes:
- External HTTP requests with slow third-party APIs
- AI nodes processing large prompts
- Database queries on large tables without filters
Debug mode and Live Logs cannot be active at the same time. Enabling one disables the other.
What's next?
| Topic | Description | |-------|-------------| | Test Terminal | Run tests from the Builder | | Live Logs | Stream production logs in real time | | Execution Logs | View historical logs in the Dashboard |