Debugging Your Workflows
Troubleshoot and resolve issues in your automated workflows.
Overview
Debugging workflows is an essential skill for maintaining reliable automation. FlowBot provides comprehensive debugging tools to help you identify, understand, and fix issues quickly. This guide covers all the debugging features and techniques available in FlowBot.
Understanding Workflow Notifications
When a workflow execution fails, FlowBot sends notifications to alert you immediately. Notifications help you stay on top of issues without constantly monitoring executions.
Accessing Notifications
- Click the bell icon in the sidebar
- View the notifications modal
- See all recent errors and informational messages
- Click on any notification to view execution details
Notification Types
- Error Notifications: Failed workflow executions
- Warning Notifications: Potential issues or warnings
- Info Notifications: Important execution updates
Notification Details
Each notification shows:
- Workflow Name: Which workflow failed
- Error Message: What went wrong
- Timestamp: When the error occurred
- Quick Actions: View execution or dismiss notification
Reviewing Workflow Executions
The executions list provides a comprehensive view of all workflow runs, helping you track performance and identify patterns.
Accessing Executions
- Navigate to Workflows in the sidebar
- Select a workflow from the list
- Click on the Executions tab
- View all executions for that workflow
Execution List Features
The executions list displays:
- Status: Success (green), Failed (red), or In Progress (blue/yellow)
- Trigger: What started the execution (Message, Webhook, Schedule, Manual)
- Started At: When the execution began
- Duration: How long the execution took
- From Number: The phone number that triggered it (for message triggers)
- Cost: Token consumption for the execution
- Actions: View details button to inspect execution
Filtering Executions
Filter executions by:
- Status: Success, Failed, In Progress
- Date Range: Last hour, day, week, month
- Trigger Type: Message, Webhook, Schedule, Manual
- From Number: Specific phone number
- Search: Find specific executions
Viewing Execution Details
Click the "View" button (eye icon) next to any execution to see detailed information about that execution.
Detailed Execution View
The detailed view shows:
Execution Overview:
- Execution ID
- Workflow name
- Trigger type and source
- Start and end times
- Total duration
- Status and outcome
- Token consumption
Visual Workflow Flow:
- Complete workflow diagram
- Each node's execution status
- Visual indicators for success/failure
- Node connections and data flow
Node Information:
- Input data for each node
- Output data from each node
- Variable values at each step
- Execution time per node
Identifying Errors in Nodes
When an execution fails, you need to identify exactly which node caused the problem.
Finding Failed Nodes
-
Open Execution Details
- Click "View" on a failed execution
- The workflow diagram opens
-
Locate Failed Node
- Look for red error indicators on nodes
- Failed nodes are clearly marked
- Execution stopped at the failed node
-
Inspect Node Error
- Click the "?" button on the failed node
- View error message and details
- Check node input/output data
Error Information
When you click the "?" button on a failed node, you'll see:
- Error Message: Specific error description
- Error Type: Category of error (API, Validation, etc.)
- Node Input: What data the node received
- Node Output: What the node produced (if any)
- Node Configuration: How the node was configured
Common Error Types
Understanding common error types helps you diagnose issues faster:
API Errors
Symptoms:
- External API call failed
- Network timeout
- Invalid API response
Common Causes:
- Invalid API URL
- Missing or incorrect API keys
- API service unavailable
- Rate limiting
How to Fix:
- Verify API endpoint URL
- Check API key configuration
- Test API endpoint independently
- Review API rate limits
Variable Errors
Symptoms:
- "Variable not found" error
- Invalid variable reference
- Variable type mismatch
Common Causes:
- Typo in variable name
- Variable not defined
- Variable scope issue
- Missing variable in context
How to Fix:
- Check variable name spelling
- Verify variable exists in scope
- Review variable definition
- Check variable type matches usage
Validation Errors
Symptoms:
- "Invalid format" error
- Data validation failed
- Type mismatch
Common Causes:
- Wrong data format
- Missing required fields
- Invalid data type
- Incorrect data structure
How to Fix:
- Review expected data format
- Check required fields are present
- Verify data types match
- Validate data structure
Template Errors
Symptoms:
- "Template not approved" error
- Template variable mismatch
- Template format error
Common Causes:
- Template not approved by Meta
- Missing template variables
- Incorrect variable format
- Template syntax error
How to Fix:
- Check template approval status
- Verify all variables are filled
- Review template syntax
- Test template separately
Timeout Errors
Symptoms:
- Execution took too long
- Node timeout exceeded
- Process timeout
Common Causes:
- Slow external API
- Large data processing
- Complex LLM operations
- Network latency
How to Fix:
- Optimize data processing
- Reduce data payload size
- Check network connectivity
- Review node configuration
Debugging Workflow
Step-by-Step Debugging Process
-
Identify the Problem
- Check notifications for errors
- Review failed executions
- Note error messages
-
Locate the Failed Node
- Open execution details
- Find the red error indicator
- Click "?" to see error details
-
Understand the Error
- Read error message carefully
- Check node input/output
- Review node configuration
-
Reproduce the Issue
- Test workflow with same input
- Verify error occurs consistently
- Note conditions that trigger error
-
Fix the Issue
- Open workflow editor
- Find problematic node
- Correct configuration or data
- Test the fix
-
Verify the Fix
- Run test execution
- Confirm error is resolved
- Monitor for similar issues
Using Test Mode
Test mode allows you to debug workflows safely:
-
Enable Test Mode
- Open workflow editor
- Click "Test" button
- Enter test data
-
Run Test Execution
- Execute workflow with test data
- View execution in real-time
- Check each node's output
-
Debug in Test Mode
- Step through workflow
- Inspect variable values
- Verify node outputs
- Test error scenarios
Best Practices
Prevention
- Test Before Deploying: Always test workflows before activating
- Validate Input: Check data formats before processing
- Handle Errors: Include error handling paths in workflows
- Use Defaults: Provide default values for optional variables
Monitoring
- Check Notifications Regularly: Review error notifications daily
- Monitor Success Rate: Track workflow success rates
- Watch for Patterns: Identify recurring issues
- Set Up Alerts: Get notified of critical failures
Debugging
- Read Error Messages: Error messages provide specific information
- Check Node Inputs: Verify data entering failed nodes
- Review Node Outputs: See what data nodes produce
- Test Incrementally: Test one change at a time
Documentation
- Document Workflows: Add notes to explain workflow logic
- Record Fixes: Note what fixes worked
- Share Knowledge: Document common issues and solutions
- Keep Notes: Maintain debugging notes for future reference
Troubleshooting Tips
Workflow not executing?
- Check workflow is active
- Verify trigger configuration
- Ensure trigger event occurred
- Check workflow permissions
Execution stuck?
- May be waiting for user input
- Check for "wait" nodes
- Verify no infinite loops
- Review node configuration
Can't see error details?
- Ensure you have permissions
- Check execution exists
- Refresh the page
- Try viewing in different browser
Error keeps occurring?
- Review error message carefully
- Check all node configurations
- Validate input data
- Test with different inputs
Need more help?
- Review workflow documentation
- Check FlowBot support resources
- Contact support with error details
- Include execution ID in support request