Execution History

Last updated: Jan 2026

Execution History lets you browse, filter, and analyze all past workflow runs. View detailed step-by-step execution data, examine outputs, track metrics like duration and cost, and compare multiple executions side-by-side.

Browsing History

Access your execution history from the Execution Pane in the workflow editor. Switch between live execution view and history mode to browse past runs.

1

Open Execution Pane

Click the Execution Pane icon in the right panel or run a workflow.

2

Switch to History Mode

Click the History button to switch from live view to history browser.

3

Select an Execution

Browse the list and click any execution to view its details.

Each Execution Shows

  • Status badge (color-coded: completed, failed, running, cancelled)
  • Timestamp and relative time
  • Duration (e.g., "2m 35s")
  • Token usage (e.g., "1.5K")
  • Cost (e.g., "3 credits")
  • Trigger type indicator (manual or scheduled)

Execution Details

When you select an execution, you can view it in three different modes depending on what information you need.

ModeDescriptionFeatures
Overview ModeHigh-level summary with progress tracking and aggregate metricsProgress ring, duration/tokens/cost totals, Gantt chart
Step Mode (Default)Detailed step-by-step breakdown of the executionCollapsible step navigation, full step details, floating stats bar
Comparison ModeSide-by-side comparison of multiple executionsCompare inputs/outputs across runs, spot differences

Step-Level Details

Click any step to see its complete execution details including inputs, outputs, tool calls, and metrics.

Detail TypeDescription
Step OutputThe result returned by this step, rendered with markdown support
Output FilesFiles generated by this step with download and "Save to Files" options
Step InputsInput parameters, files, and which upstream steps provided them. Input steps display their task content and attached files in a unified view.
Tool CallsTools invoked, their arguments, results, and execution time
Task DetailsInstructions, context, and attached files

Saving Output Files

When a step generates output files, you can save them to your permanent Files collection for reuse in other workflows.

  • Each output file displays a "Save to Files" button
  • Click the button to add the file to your Files collection
  • Saved files maintain provenance information (source workflow, execution, and step)
  • Access saved files from the Files page with source filtering

File Provenance

Files saved from executions show their origin in the Files page. The Source column displays the workflow name, helping you track which workflows generated which files.

Step Status Indicators

StatusMeaning
CompletedStep finished successfully
FailedStep encountered an error
RunningStep is currently executing
Pending ApprovalWaiting for tool or output approval

Input Step Display

Input steps have a specialized view that displays their content in a unified format. When an input step includes both task content and attached files, they are displayed as separate, selectable components.

  • Task content is shown as markdown-rendered text with copy functionality
  • Attached files display with file type icons, names, and sizes
  • Multiple components are numbered and can be selected individually
  • Files can be previewed (for images/PDFs) or downloaded

Input Files Flow Through Workflow

Files attached to an Input step are automatically available to all downstream steps. You'll see them referenced in the Inputs section of subsequent steps.

Metrics & Analysis

Use the Overview mode charts to analyze execution performance and identify optimization opportunities.

Chart TypePurpose
Duration Gantt ChartVisualize each step's execution time as horizontal bars on a cumulative timeline. Identify bottlenecks and slow steps.
Tokens Bar ChartSee token usage per step. Find steps consuming the most tokens and optimize prompts accordingly.
Cost Bar ChartView cost breakdown by step. Identify expensive operations and consider using smaller models where appropriate.
  1. Check duration charts to find slow steps: Look for steps that take significantly longer than others.
  2. Review token usage to optimize verbose prompts: High token counts may indicate overly detailed instructions.
  3. Analyze cost distribution across steps: Identify where you're spending the most.
  4. Compare metrics across multiple executions: Track improvements over time.

Comparing Executions

Compare multiple executions side-by-side to understand how different inputs affect outputs, or to debug inconsistent behavior.

Comparison Use Cases

  • Debug why one execution failed while another succeeded
  • Compare outputs from different input data
  • Analyze performance differences between runs
  • Verify consistency across scheduled executions
  • Review changes after modifying workflow configuration

Running Executions

You cannot select currently running executions for comparison. Wait for them to complete or select completed historical runs.