Job runs

The runs table lists the runs of every workflow you can view. Use it to find a run, read its status, act on it and export the list. To open a run's steps or fix a failure, see Monitor and fix a run.

Find the runs you need

1. Open Workflows in the sidebar.
2. Click a workflow card to show only that workflow's runs. Click the card again to clear the selection.
3. Type in the search box, or use the column filters, to narrow the list.

With no card selected, the table shows the runs of every workflow in view. See The Workflows screen.

Read the status

Runs can also show Skipped or Error: Skipped is muted like Aborted, and Error is shown like Failed.

A running row also shows a progress bar under its status. The bar is an estimate, based on the median duration of the last 10 finished runs of the same workflow that were not restarted. With no such runs, the bar is full. A run that takes longer than usual also keeps the bar full. The table itself shows no percentage. The node window shows the estimate as Current Progress, see Monitor and fix a run.

Read the columns

By default the table shows Job ID, Workflow Name, Start Date, Status, Duration, Execution Type, Run Scope, Current Date, Restarted and the row menu. To show more columns, click Toggle column visibility in the toolbar. Metadata ID, Pentaho ID, End Date, Extension, Error Stack and Note are hidden by default, and the row menu cannot be hidden.

Dates show the day, the month, the year and the time, for example 15/10/26 · 14:30:05.

Tell manual and scheduled runs apart

Execution Type shows who started the run. Automatic means the schedule started it. Manual means a person started it, with Run on a workflow card, or as a table sync, a transformation run, a history run, a test or a queued schema change.

Run Scope shows what the run covers:

• Workflow: a full run of the workflow.
• Single Node: one table sync, one transformation run or one history run.
• Test: a transformation test.
• Schema change: a change to a table that someone queued with Run when free because the table was busy. See When a table is busy.

Only Workflow runs are listed by default. Click the eye button on the toolbar, with the tooltip Show test, single-node and schema-change runs, to list the other runs as well; the button shows their count. Click it again, with the tooltip Hide test, single-node and schema-change runs, to hide them. See Schedules and when a workflow starts.

Filter, search and set the page size

• Hover a column header to show its filter; the filter stays visible while it is set. Duration uses a range slider, and the date columns use date filters. A day you pick covers the whole day, and the filter values match the times the cells show.
• Each column's list offers the values in the data, and the value you pick stays at the top of its list. If a list cannot load, the table warns Filter options failed and the list stays empty; try again.
• The search box searches the whole table.
• Hold a modifier key as you click a header to sort by more than one column; each sorted header shows its place in the order.
• Changing a filter, a sort or the search returns to the first page.
• The table remembers its column layout, filters, sort and page size in your browser for two hours. After that it returns to the defaults.
• When no run matches, the table shows No jobs found.

The runs table is the shared data grid. For its filters and sorting in detail, see Filter, sort and search.

Refresh and export the runs

Status, progress and the row colours update on their own while the page is open. To reload the table at once, click the refresh button, which shows the tooltip Refresh jobs.

To export the runs:

1. Set the filters, sort and search you need.
2. Choose a format in the export control: CSV, Excel, JSON or TSV. Excel is the default, and the format you choose is kept for your next export.
3. Click the download button; its tooltip reads Download as Excel, or the format you chose.
4. If more runs match than the table shows, the button opens a menu first. Choose Export N rows to save only the rows on the page, or Export all N rows to save every run that matches your filters, sort and search. Both labels show the number of rows they save. When no more runs match than the table shows, one click saves every matching run.

A full export covers up to 300,000 runs. If the export service is busy, the download fails with Export failed and Too many exports are running at the moment, try again shortly. If no run matches your filters, the download warns Nothing to export with No data to export. and saves no file.

Open a run and act on it

• Double-click a row, or click the workflow name, to open the run's steps (nodes). See Nodes in a run.
• Open the menu at the end of a row, or right-click the row, to act on the run. The menu has View, Restart, Stop, Delete and WF diagram. View opens the steps, and WF diagram shows the run as a graph; see Workflow diagram.

An action the run's status does not allow, or that you lack the permission for, is greyed out. A running run cannot be deleted; stop it first. A Schema change run has no Restart in the row menu, the context menu or the node window: it runs once, and a restart is refused with Job #<id> is a queued schema change and cannot be restarted; run the change again.

A run whose locks are still being released cannot be deleted yet: Job #<id> is still releasing its ClickHouse work (<k> lock(s)); try again when the Locks tab no longer lists it. Wait a moment and delete it again; the holders are listed in ETL locks.

If a delete is refused, you see Cannot delete with You do not have permission to delete this job. instead of the confirmation dialog.

Click the Status cell of a Failed, Running Error or Error run that has an error to open Error Stack Trace, then use Copy to copy the text. For what each action does, see Monitor and fix a run.

Check your permissions

Runs of a type you cannot view are not listed. For a Warehouse run, WF diagram also needs read access to Warehouse objects. For the full list, see Workflow permissions.

Questions, answered

Why is my table sync missing from the runs table?

A table sync you start from the Lake is a Single Node run, which the table hides by default. Click the eye button on the toolbar, with the tooltip Show test, single-node and schema-change runs. See also Run, stop and troubleshoot loads.

What is the difference between Running Error and Failed?

Running Error means a step has failed while other steps still work. When no step is left running, the run ends as Failed.

Can the progress go past 100%?

The bar in the table stops at full width and shows no percentage. The Current Progress figure in the node window is not capped, so a run that is slower than usual can show more than 100% there.

Why is a running run's progress already full?

The workflow has no finished run to compare with yet. Without one, the estimate is 100% and the bar is full. A full bar does not mean the run has finished.

How do I tell scheduled runs from manual ones?

Look at Execution Type. Automatic means the schedule started the run. Manual means a person started it. See Schedules and when a workflow starts.

Where do I find the error of a failed run?

Click the Status cell of a Failed, Running Error or Error run that has an error to open Error Stack Trace, and use Copy to copy the text. To find the failing step, open the run's steps; see Monitor and fix a run.

Does the export include only the rows on screen?

No. When more runs match than the page shows, choose Export all N rows to save every matching run, up to 300,000. Export N rows saves only the rows on the page.

Why does the Restarted column show a number I did not restart?

Restarted counts every restart, by hand or automatic. A workflow's Restart Count can restart a failed run by itself, and each of those restarts is counted. See Monitor and fix a run.

Why did I get Cannot delete when I clicked Delete?

The delete is refused. The message under Cannot delete says why. When it is a permission, you need the matching Delete permission for the run's workflow type; ask an administrator. See Workflow permissions.

Why can't I restart a Schema change run?

A queued schema change runs once. If it failed, read its error, fix the cause and make the change again on the table. See When a table is busy.

Why did my columns and filters reset?

The table keeps your column layout, filters, sort and page size in your browser for two hours. After that it returns to the defaults.