Skip to main content

Replay a trace

Replaying a trace lets you rerun a workflow from the detail of an execution, for example after an error, while being able to change the workflow version and the input data.

When to replay a trace?​

Replaying a trace is useful to:

  • Rerun a failed workflow: after fixing the workflow or the data, without waiting for the next trigger
  • Test a new version: run a revised version of the workflow with the same input data
  • Reproduce a case: replay with modified input data to debug

How to replay a trace​

Prerequisites​

Access the detail of a trace (from the Traces menu or from the Traces / Recent executions tab of a workflow). In this detail, you can already view the trigger information, the steps node by node and download the input data — see Analyze an execution.

Steps​

  1. In the trace detail, click Replay the workflow
  2. Optionally change the workflow version (by default, the version used for this execution is proposed)
  3. Optionally change the input data to replay with different parameters
  4. Choose the tracing mode for this new execution: Complete, Standard or Performance — you are no longer limited to the mode of the original execution. See Tracing modes
  5. In Complete mode, a warning banner reminds you of the impact on performance and trace volume
  6. Click Replay to start the new execution
  7. The replayed workflow is displayed; follow the new trace and find the execution history
Tip

In case of an error on a workflow, fix the workflow or the data, then use "Replay" to check the fix without waiting for the next trigger.

After replaying​

  • A new trace is created for the replayed execution
  • You can compare the old and new executions in the history
  • The new trace appears in the workflow's trace list and in the execution log (filterable by environment, status, trigger and workflow)

Next steps​