From 3b01fc9a2689c1de265fefe7dd6f641936d81766 Mon Sep 17 00:00:00 2001 From: Gleb Sologub Date: Tue, 14 Jul 2026 15:30:16 +0200 Subject: [PATCH] docs: document result freshness and pre-aggregation indicators Adds a "Result freshness and provenance" section to the workbook querying-data page (freshness leaf: refresh time, aging color, "Data age unknown", click-through to Query History; pre-aggregation bolt: "Served from a pre-aggregation"), a cross-reference from Explore, and a "Data freshness" section on the dashboards page (per-widget leaf plus the dashboard's least-recently-refreshed rollup). Co-Authored-By: Claude Opus 4.8 --- docs-mintlify/docs/explore-analyze/dashboards/index.mdx | 4 ++++ docs-mintlify/docs/explore-analyze/explore.mdx | 2 ++ .../docs/explore-analyze/workbooks/querying-data.mdx | 7 +++++++ 3 files changed, 13 insertions(+) diff --git a/docs-mintlify/docs/explore-analyze/dashboards/index.mdx b/docs-mintlify/docs/explore-analyze/dashboards/index.mdx index b79b1ffa37d00..bbfa7a64d494b 100644 --- a/docs-mintlify/docs/explore-analyze/dashboards/index.mdx +++ b/docs-mintlify/docs/explore-analyze/dashboards/index.mdx @@ -18,6 +18,10 @@ Dashboards enable you to: In the dashboard builder inside your [workbook][ref-workbooks], select the reports you want to include and arrange them on the canvas alongside other [widgets][ref-widgets] to tell your data story, then publish the dashboard. This gives stakeholders direct access to the insights that matter most, without the complexity of the underlying analysis. +## Data freshness + +Each widget shows a [freshness](/docs/explore-analyze/workbooks/querying-data#result-freshness-and-provenance) leaf indicating how recently its data was refreshed. The dashboard's own leaf reflects its least-recently-refreshed widget, so you can see at a glance whether everything on the dashboard is up to date. + ## Linking between dashboards Dashboards can link to one another. When a table widget shows a dimension that diff --git a/docs-mintlify/docs/explore-analyze/explore.mdx b/docs-mintlify/docs/explore-analyze/explore.mdx index 78b08eb72fa6d..44e29e7216cc6 100644 --- a/docs-mintlify/docs/explore-analyze/explore.mdx +++ b/docs-mintlify/docs/explore-analyze/explore.mdx @@ -45,6 +45,8 @@ Explore state is also saved in the URL, making it easy to share your exploration If you have developer or admin access, you can [apply a security context](/docs/explore-analyze/workbooks/querying-data#applying-a-security-context) to an exploration to verify what a specific end user—or an AI agent querying on their behalf—would see. +Explore results carry the same [freshness and pre-aggregation indicators](/docs/explore-analyze/workbooks/querying-data#result-freshness-and-provenance) as workbook reports. + ## Saving explorations You can save an exploration so you can return to it later without diff --git a/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx b/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx index 27ee31cb768f9..934b5c2090ebb 100644 --- a/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx +++ b/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx @@ -213,6 +213,13 @@ The **Semantic SQL** tab also has a dropdown for viewing the same query in the f These views are convenient when you want to take a query you've built interactively in a workbook and reuse it directly through one of the Core Data APIs from your own application. +## Result freshness and provenance + +Two indicators next to each result describe the data behind it. + +- **Freshness** — a leaf icon shows how recently the underlying data was refreshed. Hover over it to see the last refresh time (for example, "Refreshed 5 minutes ago"); its color shifts as the data ages, so you can tell fresh from stale results at a glance. If the refresh time can't be determined, the leaf turns gray with a "Data age unknown" label. When you have access to [Query History](/admin/monitoring/query-history), clicking the leaf opens the underlying request for that result. +- **Pre-aggregation** — for those same users, a lightning-bolt icon appears next to the leaf with a "Served from a pre-aggregation" label whenever the result was served from a [pre-aggregation](/docs/pre-aggregations). If no icon is shown, the query ran directly against your data source. + ## Editing Semantic SQL by hand You can edit the Semantic SQL directly in the editor to refine a query — for example, to add a `WHERE` clause, change `GROUP BY` order, or apply a different sort. After making changes, click **Save and Run** to apply them to the query and refresh the results, or **Discard** to revert.