Execution History

Introduction

Executions are the detailed record of every time a board runs. Each time a trigger fires — whether by schedule, webhook, or manually — a new execution is created that records all inputs, outputs, timings, and potential errors for each node.

The execution history is your primary tool for debugging and monitoring. Here you can understand exactly what happened, what data each node processed, and where something failed if there was an error.

Who This Section Is For

Operators: Who need to verify their boards are working correctly
Debuggers: Who investigate why an execution failed
Supervisors: Who monitor overall process activity

What is an Execution?

An execution is an individual instance of a board running. Its main characteristics are:

Each trigger activation creates a new execution
Records the inputs and outputs of each node
Includes timestamps for the start and end of each step
Has a status indicating whether it was successful, failed, is in progress, or paused
Allows viewing the data that passed through each node

Accessing Executions

In the left sidebar, click Execution History
You’ll see the list of all recent executions across all your boards
You can filter by board, status, or date range

Execution States

Status	Indicator	Description
✅ Success	Green	The execution completed all steps correctly
❌ Failed	Red	The execution failed at some step — check logs for details
🔄 Running	Blue	The execution is currently running
⏸️ Paused	Yellow	The execution was manually paused in Dev mode

Execution Detail

When you click on a specific execution, you can see:

Timeline

Chronological view of the execution step by step, showing:

Which node executed
How long each node took
The exact execution order

Input and Output Data

For each node, you can inspect:

Input: The data the node received
Output: The data the node produced
Error: The error message if the node failed

Logs

Detailed record of internal execution messages, useful for advanced debugging.

Dev vs Live Executions

Mode	Description	Re-executable?
🛠️ Dev	Visual execution in the editor. State is maintained in the interface and you can re-run from the editor.	✅ Yes
🚀 Live	Background execution. Recorded in history but has no automatic retry mechanism.	❌ No

Note: Currently there is no dedicated “Retry” button to re-execute failed Live mode executions. If you need to reprocess data, you must manually activate the board or trigger it again.

Execution Filters

You can filter execution history by:

Board: View only executions from a specific board
Status: Filter by success, error, running, or paused
Date range: Last 24 hours, 7 days, 30 days, or custom
Mode: Dev or Live

Common Errors

Error	Cause	Solution
”Execution failed without error message”	The node failed before it could log the error	Check the input data of the failing node — it probably received null or incorrectly formatted data
”No executions showing”	Board is inactive or trigger not configured	Verify the board is active and the trigger is properly configured
”Execution takes too long”	An external node isn’t responding or there’s too much data	Check the timeline for bottlenecks. Consider using Timer to respect rate limits

Key Terms

Execution: Individual instance of a board running, with its own data record and status
Timeline: Chronological view of executed nodes with their timings
Input/Output: Entry and exit data for each node in an execution
Log: Internal record with debugging messages
Retry: Re-execution of a failed process (available only in Dev mode)

Next Steps

Boards - Design and manage your automations
Dashboard - Activity overview
Webhooks - Configure real-time triggers