Skip to main content

Analyze an execution

This page explains how to analyze a workflow execution in detail from its trace: general information, per-node steps, input and output data, errors and history.

Before you start​

View the general information​

In the trace's detail view, the execution's general information is displayed:

  • Trace ID: unique identifier of the execution
  • Workflow: name of the workflow and executed version
  • Trigger: event at the origin of the execution
  • Status: success, failure or in progress
  • Date: execution date and time
  • Total duration: total execution time
  • Executed by New: user who started the run manually

In a trace's detail view, you can also:

  • View the trigger information
  • Download the data — the Download the data button downloads the trace payload (JSON or CSV) — see Download the data
  • Stop the workflow (if in progress)

Analyze the per-node steps​

All the steps are displayed node by node, with the level of detail that depends on the tracing mode. For each node, the following data is displayed:

  • Name: identifies the node in the workflow
  • Type: node type (HTTP(S) Request, Code, Condition…)
  • Status: success or failure
  • Duration: node execution time
  • Business metadata: annotation defined on the node, visible according to the tracing mode
  • Input data: data received by the node
  • Output data: data passed to the next nodes

Sort the steps by duration​

Click the Duration header of the steps list to sort the nodes by ascending then descending duration — handy to spot the nodes that take the most execution time.

Input data​

View the data received by the node, in JSON format (trigger data and context variables):

{
  "data": { "email": "client@example.com", "amount": 42.5 },
  "context": { "triggeredAt": "2026-08-04T09:12:00Z" }
}

Output data​

View the result produced by the node, as passed to the next nodes.

Analyze an error​

Errors are displayed on the failing node, with a detailed message and the stack trace if available.

  1. Identify the node in error.
  2. Check the error message.
  3. Verify the input data.
  4. Analyze the node logic.

View the execution history​

The history lists the executed versions and lets you compare their results — see Workflow versions.

Result​

Once the analysis is complete, you know the full sequence of the execution: trigger, status, per-node steps with their input and output data, as well as any errors. Sorting by duration highlights the nodes that take the most execution time and helps identify slow executions.

Next steps​

See also: Traces, Tracing modes, Workflow versions