Real-Time Execution View
Watch data flow through your workflow as it executes. See exactly which nodes are running, pending, or completed.
Understand exactly what's happening at each step
Visual Debugging Guide
See exactly where things go wrong. Visual debugging lets you watch data flow through your workflow, identify failures instantly, and fix issues with confidence.
8 min readAll levelsLast updated: December 2024
Debugging Features
Everything you need to understand what's happening in your workflows.
Node-Level Inspection
Click any node to see its input data, output data, configuration, and timing information.
Pinpoint where data transforms unexpectedly
Execution History
Review past executions with full trace data. Compare successful runs to failed ones to spot differences.
Learn from patterns in failures and successes
Error Highlighting
Failed nodes are highlighted instantly with detailed error messages and stack traces.
Jump directly to the source of problems
Data Flow Visualization
See how data transforms as it moves between nodes. Understand exactly what each step receives and produces.
Track data mutations across the workflow
Performance Timing
View execution time for each node and the total workflow. Identify bottlenecks slowing down your automation.
Optimize slow-running workflows
How to Debug a Workflow
Follow these steps to troubleshoot any workflow issue.
- 1
Run in Debug Mode
Click the 'Debug' button (or press D) instead of 'Run'. This enables verbose logging and step-by-step execution.
- Use sample data that matches your production scenario
- Start with simple test cases before complex ones
- Enable 'Pause on Error' for automatic breakpoints
- 2
Watch the Execution Flow
Observe the visual indicators as your workflow runs. Green means success, yellow means in-progress, red means failed.
- Nodes light up in execution order
- Connections animate to show data movement
- The timeline shows progress through parallel branches
- 3
Inspect Node Data
Click any node to open the inspection panel. View the exact input received, output produced, and any errors.
- Compare expected vs actual values
- Check for null or undefined values
- Verify data types match expectations
- 4
Identify the Root Cause
Trace backwards from the error to find where data first went wrong. Often the issue is upstream of where it manifests.
- Check the first node with unexpected output
- Look for missing required fields
- Verify API responses match expected schemas
- 5
Fix and Re-test
Make corrections to your workflow configuration and run debug again. Repeat until all nodes show green.
- Fix one issue at a time for clarity
- Re-run with the same test data for consistency
- Document fixes for future reference
Common Issues & Solutions
Quick fixes for the most frequent debugging scenarios.
Node receives 'undefined' input
Cause: Upstream node didn't produce expected output field
Solution: Check the output mapping of the previous node. Ensure field names match exactly.
API call returns 401 Unauthorized
Cause: Invalid or expired credentials
Solution: Reconnect the integration or refresh OAuth tokens in settings.
Workflow hangs on a node
Cause: External API timeout or infinite loop
Solution: Check API health, add timeout configuration, review loop conditions.
Data type mismatch
Cause: String received where number expected (or vice versa)
Solution: Add a transform node to convert types, or fix the source data format.
Conditional branch not taken
Cause: Condition logic doesn't match actual data
Solution: Inspect the condition's input data. Check for case sensitivity and type issues.
Frequently Asked Questions
Common questions about visual debugging.
Debug Workflows Like a Pro
Visual debugging makes troubleshooting fast and intuitive. See exactly what's happening at every step.