Run Explorer

The Run Explorer is the entry point into every Run your organization has uploaded. Filter by procedure, station, batch, outcome, or any metadata key; open a row to drill into phases, measurements, logs, and attachments.

Open it from Procedures → Procedure name → Runs.

Columns

Click the sliders icon at the right end of the table header to choose which columns the table shows. Columns are grouped like the filter sidebar, and your choice is saved in your browser for each organization.

Click the arrow in a column header to sort by that column. Every column sorts except Sub-units, which lists several units per row. Runs with no value in the sorted column always come last. A metadata key that holds numbers on some runs and text on others sorts numbers first, then text, then true and false values.

Filters

The filter bar combines structured filters with free-text search. Filters apply to every chart on the procedure analytics tab as well, so the explorer and the analytics dashboards stay in sync.

• Date range. Last 24 hours, 7 days, 30 days, custom range, or absolute interval.
• Outcome. Multi-select across the run outcome enum.
• Procedure version. Slice runs by the deployed version that produced them.
• Station. Limit to one or more benches.
• Batch and revision. Compare runs across production cohorts and design revisions.
• Source. Separate operator-driven runs from CLI runs.
• Operated by. Accounts and declared operator names in one list, combined as OR.
• Run metadata. Any key-value pair you attach to runs at upload time.
• Unit metadata. Any key-value pair stored on the unit each run tested.

Metadata

Every run carries a free-form metadata object you can write at upload time through the SDK, the REST API, or directly from the CLI. Keys are filterable in the toolbar, exportable as columns, and matchable in workflow triggers. See Run metadata for the schema.

Saved views

Save a filter combination as a view so the next time you open the explorer it lands on the right slice. Views live at the organization level, so anyone on your team can open the same slice from the Views menu.

Export

The Export button writes the current run set to a file. Pick the rows and the format from the dropdown.

• CSV. Flat, one row per run, with columns for outcome, procedure, unit, batch, revision, duration, timestamps, operator, and docstring.
• JSON. Nested, one object per run with the same fields plus the raw record.
• Visible vs selected. Export every visible row, or check rows in the table and export only the selection.
• Filename. tofupilot-runs-<timestamp>.<ext> so multiple exports stay distinct.

Exports honor access group scope and role permissions, so you only export the rows you can see in the table.

Permissions

The Run Explorer respects the dashboard access model:

See also