Skip to content

Traces

The trace is the run’s detail: click a run on the Runs screen and its trace flies in over the list — the whole waterfall, each event branch of the run (with its flow, status, duration, the sink that ran it, and the script-declared outcome), the module spans the sink executed, the steps a script declared, and every line inside them, with durations and statuses. The waterfall grows live while the run executes; when a run predates live traces, the detail falls back to its log records. A back row returns to the list.

Run trace


  • Branches — one header per event of the run (a trigger’s fan-out chain), with its flow, status, duration, outcome label, the branch’s progress (the script’s latest progress marker, updating live while the run executes), and a raw output link that opens the full task output in a new tab (a plain link to the presigned log URL — no fetch, so it works on every storage backend).
  • Module spans — the runner wraps every module execution automatically, so runs without script markers still get a waterfall.
  • Steps — scripts narrate their own work with step markers (see Actions & Libraries); a step’s start reads ▶ (accent) and its finish ■ with the step’s duration and result — a failed finish renders red.
  • Lines — expand a node to read its lines; structured log markers render in their level’s color (italic), and raw output lines show the script’s message without the runner’s own log header.

Traces search

The global log search is the flat table of every structured log record, searchable and filterable across runs — reachable via search all records on the Runs screen header. Clicking a record row opens that record’s run trace (with a back row to the search).

Records older than your plan’s retention are still shown here — they are read from the long-term archive. See Data Retention for how retention works on your plan.

Traces table

ColumnDescription
IDThe record’s internal id
LevelLog severity: DEBUG, INFO, WARNING, ERROR, CRITICAL
TypeThe record’s type — structured log markers fan out here (steps, status, and progress live in the trace itself, not the table)
MessageThe log message text
Event IDThe event this log belongs to
FlowThe flow the event ran in
ActionThe action that produced this log
RunShort run id — all fan-out branches of one trigger run share it
Time StampWhen the log entry was written

Traces topbar

Type in the Search logs… field in the topbar to filter by message text, level, type, flow, or action. Results update on the server as you type.

The Timespan dropdown lets you restrict logs to a time window.

PresetRange
Last 5 minNow − 5 minutes
Last 30 minNow − 30 minutes
Last 1 hourNow − 1 hour
TodayStart of today
Last 24 hoursNow − 24 hours
Last weekNow − 7 days
Custom rangePick any start and end date/time

Click Clear to remove the filter.


Use the Auto-refresh control to reload the log table automatically.

Auto-refresh control

Toggle the switch to enable, then choose an interval (10 s, 30 s, 1 m, or 5 m). Click the ↺ icon to trigger an immediate reload at any time.


ButtonAction
Edit iconOpens the log entry detail panel showing the full message and metadata
Delete iconDeletes the log record after confirmation

Select multiple rows using the checkboxes, then click Delete Selected (N) to remove them.


LevelMeaning
DEBUGVerbose diagnostic output — usually only useful when troubleshooting
INFONormal operation milestones
WARNINGSomething unexpected happened but the task completed
ERRORThe task encountered a failure
CRITICAL (50)A critical failure requiring immediate attention