There are two downloads on the run pages: Export CSV on run history, a spreadsheet of many runs, and Download the run log on one run, the whole run as a JSON file. Use the CSV for a report or an audit; use the run log to keep a full record of one run or to attach it to a support ticket.

Who can do this

Everyone in the workspace — Admin, Editor and Viewer.

Steps

Export run history as a CSV file

  1. Select Runs in the bar at the top of the page.
  2. Set the filters to the runs you want: workflow, environment, outcome and period. See Find a run in run history.
  3. Select Export CSV at the top right.

A file named like bizomate-runs-2026-10-02.csv downloads.

Download one run's log

  1. Open the run. See Find a run in run history.
  2. Select Download the run log, at the top right of the Steps box.

A file named after the run, such as run-4f21c9.json, downloads.

What happens next

Nothing changes in Bizomate; the files are copies. Each CSV row is one run with these columns: Workflow, Run, Version, Environment, Started (UTC), Duration (s), Outcome, Trigger and Error.

The run log holds the workflow's name, the run, its version, whether it was a test, the environment, the variables it used, the trigger and what it brought in, the status, when it was queued, started and finished, the error, and every step with its name, type, status, times, path taken, input, output and error.

Good to know

  • The CSV follows your filters, except Show test runs: test runs are never in the export.
  • The CSV holds up to 500 runs, the most recent that fit the filters. Narrow the period or the workflow to export older ones in parts.
  • Times in the CSV are in UTC, written as 2026-09-17 03:30:02, so they sort correctly in a spreadsheet. The page itself shows your own time zone.
  • The Run column in the CSV is a short reference — the first six characters of the run's id, such as 4f21c9 — not the run number shown on the page.
  • A workflow name starting with =, +, - or @ is written with a ' in front, so a spreadsheet does not treat it as a formula.
  • The run log contains what the run handled, including what came in with the trigger. Treat it as you would the data itself before you share it.

If something goes wrong

What you see Why What to do
The CSV has only the column headings Nothing fits the filters, or every matching run is a test run. Widen the filters. Test runs cannot be exported.
The run log cannot be found The run is no longer kept. Download logs of runs you need to keep while they are still in history.
The CSV has fewer runs than the page shows Show test runs is on, and the CSV leaves test runs out. Switch off Show test runs to see the same runs the CSV has.