Monitor runs and traces

Who can do this

Anyone who can open a workflow can see its runs and traces — minimum role User Read-Only. The organization-wide trace list requires Admin.

When a run fails — or you just want to see what happened — this page shows you how to read its history, diagnose the failure step by step, and open the full execution trace. Every workflow run is recorded with its logs, output, and steps, and traced runs add a full execution trace showing everything Ronja did and where the time went.

Browse run history

1. Open the workflow — from its feature hub row, an exploration panel, or a link in chat.
2. Scan the Activity list: each row is one run, with a status dot, a one-line summary, who ran it, and its duration. Statuses: Running, Success, Warnings, Failed.
3. Click a row to expand its inline log / output / details tabs.
4. Click Open full for the full run page — stat tiles (DURATION / TRIGGERED BY / RESULT / VERSION), tabs Output / Steps / Log, and the parameters used.

The AVG / SUCCESS / RUNS mini-stats cover recent runs, not lifetime history.

Read a failed run

1. Expand the failed row — its summary line is the error itself, and the details tab shows the parameters used.
2. Open the Log tab: a terminal view with error lines highlighted, plus Copy and Download.
3. Open the Steps tab: the failing step carries a red failed pill — expand it for the full Error block and that step’s own log.
4. Check the header if the run succeeded but shows a yellow degraded badge: a best-effort step failed without sinking the run, and the Steps tab tells you which one.
5. Click the re-run icon (top right) to replay the run with the same parameters.

Open the execution trace

1. Click View trace in the run page header (shown when the run was traced).
2. Read the health card — “Completed — no issues”, “Completed with {N} issue(s)”, or “Failed” — and the four tiles: TOOK, STEPS, RAN IN PARALLEL, FINISHED.
3. Scan the waterfall: one row per span in the causal chain — an AUTOMATION trigger, the WORKFLOW RUN, its STEPs, any AI · AGENT work — all on one shared time axis. A bracket and a purple “parallel” chip mark steps that ran at the same time.
4. Expand a failed span’s Error & logs disclosure for the full error text.

The execution trace: “What Ronja did, step by step — and where the time went.”

Note

Traces are retained for about 30 days. Runs from before tracing existed simply have no View trace link.

In an exploration

1. Click the pinned Runs entry on the session’s rail — it lists every workflow and Saved Agent run this conversation spawned.
2. Click a row to open its trace in a docked panel. Run cards in chat also carry their own View trace button.

Organization-wide (admins)

Admins can open the Activity Overview’s Traces tab for a newest-first list of every execution trace in the organization, with Load more paging — see Monitor activity and usage.