Skip to content

Execution detail

The full record of one execution. Open it at /logs/<execution id>, with View details on an expanded row in Logs, or with Open log details in the editor's executions list.

The Execution Details page on the Overview tab: "Workflow failed at: Fetch invoice", the Performance Metrics and AI Cost & Usage cards, and the Execution Timeline with three successful nodes and the failed one.The Execution Details page on the Overview tab: "Workflow failed at: Fetch invoice", the Performance Metrics and AI Cost & Usage cards, and the Execution Timeline with three successful nodes and the failed one.

  • The title Execution Details.
  • Two tabs: Overview and Output.
  • The Workflow ID, with a button to copy it.
  • Go to Workflow, which opens the workflow in the editor.

The page is for reading. To rerun or stop a run, use the editor. See Rerun, stop & pause.


Overview tab

State card

A one-line summary of the run:

Run The card shows
Success "Workflow successful", "Executed to completion", and whether a live trigger or a manual run started it
Failed "Workflow failed at: ", the error message, and an error reference you can copy for a support ticket
Waiting "Waiting for Approval", the node it is paused at, and how many steps are done
Stopped "Stopped before it finished."
Still running "This run has not finished yet."

Performance Metrics

Total Time, Nodes Executed, Successful, Failed, Slowest Node and Skipped.

AI Cost & Usage

For runs with AI nodes: API Calls, Token Cost, Total Tokens and Models Used. Click View breakdown for each call.

Execution Timeline

One row per node that ran, in order.

Column Notes
Status The node's status
Node Name
Started At / Finished At
Duration
Description What the node did, or its error

Tags mark rows that need attention: Failed, Slow and AI.

Workflow Structure

A read-only canvas of the workflow as it ran, with each node coloured by its status. Click a node to select it.

The Workflow Structure canvas of a failed run: three nodes marked green, Fetch invoice marked red, and the two nodes after it grey because they never ran.The Workflow Structure canvas of a failed run: three nodes marked green, Fetch invoice marked red, and the two nodes after it grey because they never ran.

Execution Information

Execution ID, Workflow ID, Triggered By, Started At, Finished At and Environment.

Workflow Information

The workflow's Name, Version, Last Modified By and Tags.


Output tab

The final result of the run, as formatted JSON.

  • Expand and Collapse open or close every level.
  • Copy JSON copies the whole result.

To see what each node produced, open the run in the editor and click the node. See Reading node output.


Tips & gotchas

  • The canvas shows the version that ran. If you have edited the workflow since, it differs from what you see in the editor.
  • A node that hit its Timeout shows as Failed. Read its error message for the cause.
  • Cost figures are estimates, worked out from each provider's prices at the time of the run.
  • Share a run by its URL. Anyone in the workspace who can open the workflow can open /logs/<execution id>.


Found something out of date? This page lives in the Flero docs content set.