Skip to main content
Version: v2.10.0

Workspace Runs

The Runs tab is the landing tab of a Workspace. It combines a statistics strip summarising every run in the Workspace with a filterable table of the individual run records for Jobs and Notebooks.

Route:

/workspace/<id>/runs?pageNumber=1&limit=20

Workspace Runs tab showing the Workspace Statistics strip and the run table with all fourteen columns

Workspace Statistics

A card headed Workspace Statistics sits above the table. It holds eight counters: TOTAL COUNT plus one counter for each of the seven run statuses. Each counter carries its own status icon and colour, matching the icon rendered in the Status column of the table below. The seven statuses counted are DONE, SUBMITTED, RUNNING, STOPPING, STOPPED, TERMINATED and ERROR.

CounterWhat it counts
TOTAL COUNTEvery run recorded in this Workspace.
DONERuns that completed successfully.
SUBMITTEDRuns accepted and waiting to start.
RUNNINGRuns currently executing.
STOPPINGRuns in the process of being stopped.
STOPPEDRuns that were stopped.
TERMINATEDRuns that were terminated.
ERRORRuns that failed.

Toolbar

ControlDescription
Clear all filtersRemoves every active column filter in one click.
RefreshRe-fetches the run list.
Column optionsOpens a popover of toggleable optional columns.
Search-mode selectorA dropdown with two options, Job Name (default) and Run ID, that decides what the adjacent search input matches.
Search inputFilters the table by the value chosen in the selector. With Job Name selected the placeholder reads Enter job name....

The Column options popover controls exactly four columns, which you can show or hide:

  • Created By
  • Modified By
  • Start Time
  • End Time

Columns

The table has 14 columns.

ColumnDescription
Run IDIdentifier of the run, rendered as a link. Sortable.
StatusRun status, shown as a status chip with an icon. Filterable.
NameName of the Job or Notebook, rendered as a link. Notebook runs also show a small preview icon after the name. Sortable.
TypeWhat kind of workload produced the run. Filterable.
LanguageLanguage the run executed in. Filterable.
Cluster NameCluster the run executed on. Filterable.
Total Duration TimeTotal wall-clock duration of the run. Sortable.
Execution TimeTime spent actually executing. Sortable.
Approx YCUApproximate Yeedu Compute Units consumed. Its ⓘ tooltip reads: YCU stands for Yeedu Compute Unit. 1 YCU/hour = Cores/4 + Memory/10.
Created ByUser who created the run. Filterable. Optional column.
Modified ByUser who last modified the run. Filterable. Optional column.
Start TimeWhen the run started. Optional column.
End TimeWhen the run ended. Optional column.
ActionsA single Stop button.

Actions column

The Actions column holds one Stop button and nothing else. There's no kebab menu on this table. We render the button disabled for runs that can't be stopped, such as runs already in STOPPED or DONE.

AssistantX on failed runs

We put an AssistantX icon beside the status chip on rows whose status is ERROR. Use it to get a one-click diagnosis of why the run failed.

Filtering

Columns marked as filterable carry a filter icon in the header. Clicking it opens a filter popover containing:

  • a checkbox list of the available values,
  • a summary line that reads No selected item until you tick something,
  • a Clear button that unticks everything, and
  • an Apply button that commits the selection to the table.

Status filter popover on the Runs table, showing the checkbox list with Clear and Apply buttons

Cluster Name, Created By, and Modified By are data-driven. Their checkbox lists are built from the clusters attached to the Workspace and the users present in the run history. Status, Type, and Language are fixed enumerations, listed below.

Status

Value
SUBMITTED
RUNNING
DONE
ERROR
TERMINATED
STOPPING
STOPPED

Type

Value
JAR
Functions
Custom Code
Notebook
Thrift SQL

Language

Value
Raw Scala
Python
Python3
Scala
Thrift SQL
SQL
Spark SQL
note

The values above are listed in the order they appear in each filter popover.