Traces
Traces let you track and analyze the execution of your workflows.
Every workflow execution generates a trace that you can view, analyze and, if needed, replay. The level of detail recorded depends on the configured tracing mode (Full, Standard or Performance).
What is a trace?
A trace represents a workflow execution. The level of detail depends on the configured tracing mode (Full, Standard or Performance) — see Tracing modes.
In general, a trace lets you:
- Track the execution steps according to the chosen mode
- View the data and errors useful for diagnosis
- Debug and optimize your workflows
- Keep a history of executions
Available information
Depending on the tracing mode, the trace may include notably:
- Workflow: name of the workflow and executed version
- Trigger: event at the origin of the execution
- Status: success, failure or in progress
- Data: inputs / outputs per node (depending on the mode)
- Timing: execution time when node detail is kept
- Errors: messages and details about failing nodes
Usage
Traces are used to:
- Debug: identify issues
- Optimize: analyze performance
- Audit: track executions
- Monitor: watch the health of workflows
In case of an error, check the trace to see exactly which node the problem occurred at and which data was available at that moment. To rerun a corrected execution without waiting for the next trigger, see Replay a trace.
The Traces assistant on Chat Ecosystem helps analyze your execution traces with the full context of your organization — see Chat Ecosystem Assistant.