Debugging Errors

When workflows fail, you need to quickly identify and fix the issue. This guide covers common errors and debugging techniques.

Finding the Error

In the Editor

Failed nodes show a red indicator:

1. Look for nodes with red borders
2. Click the node to see the error
3. Check the Errors tab in the panel

In Execution Logs

1. Go to Executions tab
2. Find the failed run
3. Click to open details
4. See which node failed and why

Common Error Types

Connection Errors

Symptoms: "Connection refused", "Timeout", "Network error"

Causes:

• External service is down
• Network issues
• Firewall blocking requests

Solutions:

• Check if the external service is available
• Verify the URL is correct
• Check your network configuration

Authentication Errors

Symptoms: "401 Unauthorized", "403 Forbidden", "Invalid credentials"

Causes:

• Expired OAuth token
• Wrong API key
• Missing permissions

Solutions:

• Refresh the integration connection
• Verify API key is correct
• Check required scopes/permissions

Validation Errors

Symptoms: "Invalid input", "Missing required field", "Type mismatch"

Causes:

• Missing required data
• Wrong data format
• Type mismatches

Solutions:

• Check input data structure
• Verify required fields exist
• Use conditions to handle missing data

Rate Limit Errors

Symptoms: "429 Too Many Requests", "Rate limit exceeded"

Causes:

• Too many API calls
• Exceeding service limits

Solutions:

• Add delays between requests
• Batch operations where possible
• Upgrade API plan if needed

Debugging Techniques

1. Check Input Data

View what data the node received:

1. Click the failed node
2. Go to Input tab
3. Verify data structure and values

2. Test in Isolation

Run just the failing portion:

1. Create a test workflow
2. Add only the failing node
3. Provide known-good test data
4. Identify if node or data is the issue

3. Add Logging

Insert log nodes to track data:

1. Add a Log node before the failing node
2. Output the data being passed
3. Run the workflow
4. Check logs for unexpected values

4. Simplify

Remove complexity to isolate the issue:

1. Remove conditional branches temporarily
2. Use hardcoded values instead of variables
3. Test each piece individually
4. Rebuild once working

5. Check Variable Paths

Ensure variables resolve correctly:

1. Open the variable picker
2. Verify the path exists
3. Check for typos
4. Handle null cases with defaults

Error Handling

Try-Catch Pattern

Wrap risky operations:

1. Add an Error Handler node
2. Connect it to nodes that might fail
3. Define fallback behavior
4. Log errors for investigation

Retry Logic

Automatically retry transient failures:

1. Enable Auto-retry on the node
2. Set retry count (e.g., 3)
3. Set delay between retries
4. Works for timeout and connection errors

Fallback Actions

Define what happens on failure:

1. Send notification to yourself
2. Log error details
3. Use default values
4. Skip non-critical operations

Node-Specific Debugging

HTTP Request

Common issues:

• Wrong URL: Double-check the endpoint
• Missing headers: Add required auth headers
• Bad body format: Verify JSON structure
• Wrong method: POST vs GET matters

Debug tips:

• Use a tool like Postman first
• Log the request before sending
• Check response status codes

Condition

Common issues:

• Wrong branch taken: Verify comparison values
• Type mismatch: String "5" != Number 5
• Case sensitivity: "Active" != "active"

Debug tips:

• Log the value before the condition
• Check for whitespace
• Use explicit type conversion

Loop

Common issues:

• Empty array: No iterations happen
• Null item: Check for null in array
• Performance: Large arrays slow down

Debug tips:

• Log array length
• Add condition to skip null items
• Limit iterations for testing

Getting Help

If you can't resolve the issue:

1. Check documentation - Search the help center
2. Community forum - Others may have solved it
3. Contact support - Include execution ID and error details

When reporting:

• Include the workflow ID
• Include the execution ID
• Describe expected vs actual behavior
• Share relevant error messages

Next Steps

• Execution Logs - View all runs
• Manual Execution - Test workflows
• Using Variables - Fix variable issues