Executions

The Executions view provides visibility into workflow runs, including detailed step-by-step logs, timing information, and error tracking.

Execution List

Viewing Executions

Navigate to Automation > Executions to see:

Filtering Executions

Filter by:

• Workflow name
• Status (success, failed)
• Date range
• Trigger type

Execution Details

Overview

Click an execution to view:

• Overall status
• Start and end times
• Total duration
• Trigger information

Step Details

Each step shows:

Data Inspection

View input and output for each step:

{
  "input": {
    "order_id": "ORD-001",
    "customer": "John Doe"
  },
  "output": {
    "success": true,
    "message": "Email sent"
  }
}

Execution States

Status Types

Step States

Error Tracking

Viewing Errors

Failed executions show:

• Error message
• Stack trace (if available)
• Step that failed
• Input data at failure

Common Error Types

Debugging

To debug a failed workflow:

1. Open the execution
2. Find the failed step
3. Review input data
4. Check error message
5. Fix workflow and retry

Execution History

Retention

Execution history is retained based on system settings:

• View historical executions
• Analyze patterns over time
• Identify recurring issues

Statistics

For each workflow:

• Total executions
• Success rate
• Average duration
• Recent failures

Manual Execution

Running Workflows

Execute workflows manually:

1. Open the workflow
2. Click Execute
3. Provide input data (if needed)
4. Watch execution progress

Testing Changes

Before enabling a workflow:

1. Make changes in editor
2. Execute manually
3. Verify results
4. Enable for production

Monitoring

Active Executions

View currently running workflows:

• Real-time status
• Step progress
• Option to cancel

Alerts

Configure alerts for:

• Failed executions
• Long-running workflows
• Specific error types

Best Practices

Regular Review

• Check failed executions daily
• Review error patterns
• Address recurring issues

Performance

• Monitor execution duration
• Identify slow steps
• Optimize HTTP timeouts

Debugging

• Use log actions for visibility
• Add descriptive step names
• Include relevant data in logs