Skip to main content

Executions

Once your workflows are active, you need to monitor them. This page explains what executions are, how to track and inspect runs, read logs and status, replay runs on the canvas, and handle failures.

Time to complete: 15 minutes

Execution Overview​

Every time a workflow runs, it creates an execution - a record of what happened, when, and what data was processed.

What's Tracked​

DataDescription
Execution IDUnique identifier for this run
StatusPending, Running, Completed, Failed
Start TimeWhen execution began
End TimeWhen execution finished
DurationTotal time taken
Trigger DataWhat started the workflow
Node ResultsInput/output for each node
ErrorsAny failures that occurred

Accessing Executions​

From the Workflow Builder​

  1. Open your workflow in the builder
  2. Click the Executions tab (bottom panel)
  3. See recent executions for this workflow
┌─────────────────────────────────────────────────────────────┐
│ Executions                                                   │
├─────────────────────────────────────────────────────────────┤
│ ID          Status      Started           Duration    ▶️    │
│ ex_abc123   ✅ Completed  2 min ago        1.2s       [→]   │
│ ex_def456   ✅ Completed  15 min ago       0.8s       [→]   │
│ ex_ghi789   ❌ Failed     1 hour ago       0.3s       [→]   │
└─────────────────────────────────────────────────────────────┘

From the Executions Page​

  1. Navigate to Automation → Executions
  2. See all executions across all workflows
  3. Filter by workflow, status, date range

The execution list shows:

  • Status (success, failed, running)
  • Duration
  • Trigger type
  • Start time
  • Workflow name

Execution States​

StateIconMeaning
Pending⏳Queued, waiting to start
Running🔄Currently executing
Completed✅Finished successfully
Failed❌Error occurred
Cancelled🚫Manually stopped
Waiting⏸️Paused for input
Timed Out⏱️Exceeded time limit

Viewing Execution Details​

Click on any execution to see full details.

Execution Summary​

┌─────────────────────────────────────────────────────────────┐
│ Execution: ex_abc123                                         │
├─────────────────────────────────────────────────────────────┤
│ Status:     ✅ Completed                                     │
│ Workflow:   Welcome Email Automation                         │
│ Started:    Mar 15, 2024 10:30:15 AM                        │
│ Ended:      Mar 15, 2024 10:30:16 AM                        │
│ Duration:   1.2 seconds                                      │
│ Nodes Run:  5 of 5                                          │
└─────────────────────────────────────────────────────────────┘

Trigger Data​

See what data triggered the workflow:

{
  "payload": {
    "email": "john@example.com",
    "name": "John Smith",
    "source": "signup_form"
  },
  "headers": {
    "Content-Type": "application/json"
  },
  "method": "POST"
}

Timeline & Node-by-Node Results​

The timeline shows node-by-node execution order, timing for each node, and the data at each step. Each node shows its execution details:

┌─────────────────────────────────────────────────────────────┐
│ 1. Webhook Trigger                                   ✅ 12ms │
├─────────────────────────────────────────────────────────────┤
│ Input:  (trigger data)                                       │
│ Output: { payload: { email: "john@example.com", ... } }     │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ 2. Transform Data                                   ✅ 5ms  │
├─────────────────────────────────────────────────────────────┤
│ Input:  { webhooktrigger_1: { payload: ... } }              │
│ Output: { formatted_email: "john@example.com", ... }        │
└─────────────────────────────────────────────────────────────┘

Understanding Node Execution​

Input Data​

What the node received from upstream nodes:

{
  "webhooktrigger_1": {
    "payload": {
      "email": "john@example.com"
    }
  }
}

Output Data​

What the node produced:

{
  "success": true,
  "message_id": "msg_abc123",
  "recipient": "john@example.com"
}

Execution Duration​

Time taken by each node:

NodeDurationTypical Range
Trigger5-20msFast
Transform1-10msVery fast
Condition1-5msVery fast
Email Send100-500msDepends on provider
API Request100-2000msDepends on external API
LLM500-5000msDepends on model

Execution Replay​

Replay lets you visualize an execution on the workflow canvas, stepping through the exact state at each node.

How to Replay​

  1. Open execution details
  2. Click Replay on Canvas button
  3. Workflow opens with execution data loaded
  4. Nodes highlight as they executed
  5. Click any node to see its data

What You See​

VisualMeaning
Green borderNode completed successfully
Red borderNode failed
Gray dashedNode was skipped
NumbersExecution order
Duration badgesTime per node

Using Replay for Debugging​

  1. Replay a failed execution
  2. Click on the failed node (red border)
  3. View the Input tab - what data did it receive?
  4. View the Error tab - what went wrong?
  5. Identify the issue
  6. Fix and re-test

Debugging Features​

Step-by-Step Replay​

  1. Open execution
  2. Click through nodes
  3. See exact state at each step

Re-run from Node​

  1. Select failed node
  2. Click Run from Here
  3. Execution continues from that point

Single Node Test​

  1. Select node in builder
  2. Click Run
  3. Execute just that node with test data

The Execution Panel​

The bottom panel shows executions while you work.

Panel Sections​

┌─────────────────────────────────────────────────────────────┐
│ [Executions] [Logs] [Console]                               │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│ Recent executions appear here...                            │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Executions tab: List of workflow runs Logs tab: Real-time execution logs Console tab: Debug output (console.log)

Real-time Updates​

The panel updates automatically:

  • New executions appear at the top
  • Status updates in real-time
  • Click to expand details

Filtering Executions​

By Status​

Status: [All ▼]
        ├── All
        ├── Completed
        ├── Failed
        ├── Running
        └── Pending

By Date Range​

From: [Mar 1, 2024]
To:   [Mar 15, 2024]

By Workflow​

Workflow: [All Workflows ▼]
          ├── All Workflows
          ├── Welcome Email Automation
          ├── Lead Scoring
          └── Daily Report

By Trigger Type​

Filter executions by the trigger that started them.

Search by:

  • Execution ID
  • Trigger data content
  • Error messages

Execution Logs​

Log Levels​

LevelPurpose
INFONormal operations
DEBUGDetailed debugging
WARNPotential issues
ERRORFailures

Reading Logs​

[10:30:15.123] INFO  Execution started: ex_abc123
[10:30:15.135] INFO  Node webhooktrigger_1 completed (12ms)
[10:30:15.140] DEBUG Transform input: { email: "john@..." }
[10:30:15.145] INFO  Node transformdata_1 completed (5ms)
[10:30:15.650] INFO  Node emailsend_1 completed (500ms)
[10:30:16.320] INFO  Execution completed (1.2s)

Logs also include API calls and error stack traces.

Console Output​

If you use console.log in Transform nodes:

console.log("Processing contact:", contact.email);

Output appears in Console tab:

[Console] Processing contact: john@example.com

Execution Metrics​

Available Metrics​

MetricDescription
Total ExecutionsCount of all runs
Success Rate% completed successfully
Failure Rate% that failed
Avg DurationAverage execution time
ThroughputExecutions per hour

Viewing Metrics​

┌─────────────────────────────────────────────────────────────┐
│ Last 7 Days                                                  │
├─────────────────────────────────────────────────────────────┤
│ Total:     1,234 executions                                 │
│ Success:   1,198 (97.1%)                                    │
│ Failed:    36 (2.9%)                                        │
│ Avg Time:  1.8 seconds                                      │
└─────────────────────────────────────────────────────────────┘

Handling Failed Executions​

Identifying Failures​

Failed executions show:

  • ❌ Red status indicator
  • Error message
  • Failed node highlighted

Common Failure Reasons​

ReasonExampleSolution
Missing dataVariable undefinedAdd validation
Invalid inputMalformed emailAdd format check
External failureAPI timeoutAdd retry logic
Auth failureToken expiredRefresh integration
TimeoutExecution too longOptimize workflow

Retry Failed Execution​

  1. Open failed execution
  2. Click Retry button
  3. Execution runs again with same input
  4. Check if it succeeds

Manual Resolution​

  1. Identify the issue
  2. Fix the workflow or data
  3. Manually trigger with corrected data

Monitoring Patterns​

Daily Health Check​

  1. Go to Executions page
  2. Filter by last 24 hours
  3. Check failure rate
  4. Investigate any failures

Failure Alerting​

Set up alerts for failures:

  • Create a workflow that triggers on execution failure
  • Send Slack notification or email
  • Include error details

Performance Tracking​

Monitor execution duration:

  • Track average duration over time
  • Identify slow nodes
  • Optimize bottlenecks

Best Practices​

1. Monitor Regularly​

  • Check executions daily
  • Set up failure alerts
  • Review weekly metrics

2. Keep Execution History​

  • Don't delete old executions immediately
  • Useful for debugging recurring issues
  • Helps identify patterns

3. Use Meaningful Names​

  • Name workflows descriptively
  • Use custom node aliases
  • Makes logs easier to read

4. Add Logging​

// In Transform nodes
console.log(`Processing order ${order.id}`);
console.log(`Total value: $${order.total}`);

5. Test Before Activating​

  • Use Test mode first
  • Review execution data
  • Activate only when confident

Quick Reference​

Execution States​

⏳ Pending    - Queued
🔄 Running    - Executing
✅ Completed  - Success
❌ Failed     - Error
🚫 Cancelled  - Stopped
⏸️ Waiting    - Paused for input
⏱️ Timed Out  - Too long

Access Executions​

Builder   → Bottom panel → Executions tab
Global    → Automation → Executions
Workflow  → Click workflow → View Executions

Execution Data​

Trigger Data  - What started it
Node Inputs   - Data received by each node
Node Outputs  - Data produced by each node
Duration      - Time per node
Errors        - Failure details

Common Actions​

View Details  - Click execution
Replay        - Visualize on canvas
Retry         - Run again
Filter        - By status/date/workflow
Search        - By ID/content/error

Next Steps​

Continue with:

  1. Debugging Workflows - Fix execution issues
  2. Error Handling - Prevent failures
  3. Best Practices - Optimize monitoring
Last updated on