🤖 Explain with AI

Workflow Execution¶

Test, run, and monitor workflows with detailed execution logs and step-by-step status tracking.

Overview¶

Workflow Execution provides:

• Test Runs — Execute workflows in test mode before activating
• Execution Logs — Step-by-step status with input/output data
• Run History — View past workflow executions
• Real-Time Monitoring — Live progress tracking
• Error Handling — Detailed error messages and troubleshooting

Test Runs¶

What is a Test Run?¶

A test run executes a workflow without marking it as a production run. It’s used to verify that all steps work correctly before activating the workflow.

Running a Test¶

1. Navigate to the Workflow Builder
2. Click Test Run in the top-right corner
3. The workflow executes:
4. All steps run in sequence
5. Real-time progress is displayed
6. Results are shown for each step
7. Review the execution log
8. Fix any issues
9. Run another test if needed

Test Run Behavior¶

Execution Logs¶

Log Panel¶

The execution log panel appears at the bottom of the Workflow Builder during and after execution:

Step Status¶

Viewing Step Details¶

Click on a step to expand and view:

Overall Status¶

Run History¶

Viewing Past Runs¶

1. Navigate to Workflows from the main menu
2. Click on a workflow
3. Click Execution History

History Table¶

Viewing Run Details¶

Click on a run to view the full execution log with step-by-step details.

Real-Time Monitoring¶

Live Progress¶

During execution, the log panel updates in real-time:

1. Steps change from Pending → Running → Success/Failed
2. Duration updates as each step completes
3. Input/output data appears as steps finish
4. Overall status updates when all steps complete

Polling¶

The frontend polls workflow_execution_steps every 1.5 seconds to track progress. Up to 60 polling attempts are made (90 seconds total).

Expression Resolution¶

Step References¶

Reference data from previous steps using the expression syntax:

{{Step N.field}}

Examples: - {{Step 1.output.contact_id}} — Contact ID from Step 1 - {{Step 2.output.event_id}} — Event ID from Step 2 - {{Step 1.output.email}} — Email from Step 1

Trigger References¶

Reference data from the trigger:

{{trigger.field}}

Examples: - {{trigger.email}} — Email from webhook payload - {{trigger.phone_number}} — Phone number from webhook - {{trigger.customer_name}} — Customer name from trigger

Nested References¶

Reference nested fields in JSON objects:

{{Step 1.output.customer.email}}
{{trigger.data.address.city}}

Error Handling¶

Step Failures¶

When a step fails:

1. The step status changes to Failed
2. An error message is displayed
3. All subsequent steps are marked as Skipped
4. The overall workflow status becomes Failed

Common Errors¶

Retry Logic¶

The workflow engine implements:

• Automatic Retries — Failed actions retry with exponential backoff
• Max Retries — Configurable maximum retry attempts
• Dead Letter Queue — Failed messages after max retries

Production Runs¶

Activating a Workflow¶

1. Navigate to the Workflow Builder
2. Click Activate in the top-right corner
3. The workflow becomes active and will be triggered by:
4. Manual runs
5. Scheduled triggers (cron)
6. Webhook triggers

Deactivating a Workflow¶

1. Navigate to the Workflow Builder
2. Click Deactivate
3. The workflow stops accepting new triggers
4. In-progress executions continue to completion

Best Practices¶

1. Always test first — Run a test before activating
2. Use descriptive step names — Makes debugging easier
3. Handle empty results — Use conditions to handle missing data
4. Monitor execution logs — Check for errors regularly
5. Set appropriate timeouts — Prevent long-running steps
6. Use idempotent actions — Ensure safe retries

What’s Next¶

• Triggers — Configure when workflows run
• Actions — Explore available actions
• Templates — Use pre-built workflow templates
• FAQ — Common questions about workflows

Still questions? Ask on Discord or explore tutorials