Workflow Logs Screen

Open Workflow logs from the main navigation to search v1 Runtime and v2 Runtime execution evidence across the current Site. Opening logs from a Workflow preselects that Workflow and provides a Back action to its landing screen.

Search controls

Control Behaviour
Workflow Selects one Workflow or All Workflows. v2 Runtime entries carry a badge.
Node Selects one Node, Start, or the context-dependent all option. v2 Runtime Nodes carry a badge.
Search text Uses indexed content search when that Site feature is available. While text is present, Workflow, Node, result, and time controls are constrained because the indexed query owns the search.
Result Selects all results or errors.
Date and time Sets the end of a 24-hour search window.
Search button Runs a new query for up to 100 rows.

When troubleshooting, use indexed search to locate matches to a fragment of data like an invoice number or transaction identifier.

Results and row selection

The search result rows show the Workflow and instance (the two coloured circles on the left-hand side can be used to visually pick out a Workflow or instance of interest). The Workflow column shows its name, with runtime and Environment badges where available. The logs also present start time, duration, Step or Node, execution output, and result. Child activity, including container iterations or Sub-Workflow relationships, is visually nested where the log format supports it.

Select a row to change the Property columns to the inputs (parameters) and outputs (returns) available for that row. Non-text values will be presented as downloadable files. Large values may only be partially logged, which will be indicated in the log. This particularly applies to v2 Runtime collection parameters and returns.

Although logs are internally stored in UTC, the Console will present them in the browser's local time zone. Use the exact timestamp and Environment metadata in the activation record when correlating with another system.

For a v2 Runtime activation, inspect the Start Step's Parameters for its Context. A log entry for an invocation without a Workflow identity has no Workflow designer link; instance-level log actions can still be available.

On-screen filter and download

After results load, use the local filter/search control to narrow or highlight text in the loaded rows. This only filters or highlights rows that have been loaded into the Console; it does not run a server-side query.

Download CSV exports the loaded log rows and their available columns. A download reflects current returned evidence; it does not retrieve omitted, redacted, expired, or separately stored values.

Use Load entries before <time> to page backwards for non-indexed searches.

Runtime boundaries

For live v2 Runtime Debug output, use Designer Console and Logs. See Workflow Logging and Missing or Incomplete Log Data.

See also