Work with query results

← Analyze

Explore keeps a run record for each submitted analysis. The result of the run you are viewing appears directly under the query.

Read a result

The result header shows the run’s status, duration, start time, and icons to Copy link, Download result, and Close result. Semantic runs have Table, Chart, and SQL tabs; SQL runs have Table and SQL. Beside the tabs, a short status says how much of the result you are looking at, such as 48 rows or First 20 of 48 rows.

• Table shows up to 1,000 rows. When the result is larger, the status reads First N of M rows; sorting by a column header then orders only those preview rows, so add a sort to the Metrics query, or ORDER BY to a SQL query, to order every row. A Metrics query without a sort opens in time order, earliest first, when it is grouped by time. Metric values use the display format saved when the run started. Without a metric format, decimals show every digit the values need, without warehouse padding, and are never rounded. Hover a cell for the value as returned.
• Chart draws a Semantic result exactly as returned: lines for a time axis, bars for one category, and a large number for each metric when the query has no group-by. It draws only a complete result; if the result is larger than the preview or stopped at its row limit, use a coarser granularity, fewer group-bys, or a filter.
• SQL shows the SQL that ran. For a Semantic run, Open in SQL copies it into the SQL editor without running it.

Times in a Metrics result are in the Workspace’s Reporting time zone, and a result that groups or filters by time names it, such as Times in Asia/Seoul. Day, week, month, quarter, and year values are dates, and a week is labeled by its Monday. Hour and finer values are wall-clock times in that zone. A result keeps the zone it ran with, even if the Workspace’s zone changes later. SQL results show what your SQL returns. See Time zones and dates.

A metric can use Number, Currency, or Percent with 0–6 decimal places. Currency uses its saved ISO code; Percent displays a ratio such as 0.125 as 12.5%. A small nonzero value expands its decimal places so it does not read as zero. Changing a metric format affects new runs; earlier runs retain their saved format. Sorting, copying raw values, and downloads retain the original values. Chart tooltips format the original decimal for each point.

A failed run opens on Why it failed, which explains the cause, links to what to fix, and offers Run again; its SQL stays on the SQL tab.

Copy link copies a link to this exact run. Any Explorer or higher in the workspace can open it, and you can hand it to an agent.

Inspect or cancel a run

Open Runs in Explore; on a wide screen the run list is shown beside the composer. Opening a run shows its result and restores its query into the composer. A queued or running item has not completed. If you no longer need it, select Cancel and wait for a final outcome.

Editing the restored query does not change the earlier run; a warning above the result says Query edited since this run. Select Run in that notice to start a new run. If opening a run replaced a query you hadn’t run yet, select Restore it to bring it back.

Download a completed result

Select the Download result icon above the completed result, then Download CSV or Download Arrow original. Downloads work in all browsers: where the browser supports direct file saving, such as Chrome or Edge, you choose the destination and the file is written as it arrives; elsewhere it is saved as a normal download. CSV downloads have a 1 GB maximum. Cancel download stops file saving; it does not cancel a completed query.

The bottom of the download menu shows Available until; a result can be viewed and downloaded for 3 days after the run succeeds. If saving fails, retry after resolving the displayed error; an incomplete download is not a successful export.

Agents follow the run’s availableOperations to read its returned result path. To request an Arrow download reference, call monomer_read with the real result path and "download": "arrow". Use the returned short-lived link promptly and keep it private. For a new run, follow the collection’s advertised run entry and fetch its input schema with monomer_describe before constructing the call, as shown in Run SQL and Analyze a metric.

Revisit earlier work

Select a previous item in Runs. Access to historical output still depends on current workspace membership and data permissions. A run whose result has expired still opens with its query and its SQL, so you can select Run again if you still need the result. The new result can differ because source data or metric definitions may have changed.

For a reusable team view, create a dashboard. For a narrative report, upload a document.