From 2a45884d22e8dde2bc09f801abe33d5a787b8869 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 5 Sep 2026 00:13:59 +0000 Subject: [PATCH] docs: describe the outcome messages after a manual pre-aggregation refresh MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A chart's Refresh, a dashboard's Refresh all, and a workbook's Run all now report whether a pre-aggregation rebuild actually completed, was only requested, or is still running — rather than assuming success. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_011oxbph2zZPPPv8NCMRofH4 --- docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx b/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx index 297bb97b528d3..4d17efeb5a899 100644 --- a/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx +++ b/docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx @@ -334,6 +334,8 @@ 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. +Manually refreshing a result served from a pre-aggregation (a chart's **Refresh**, a dashboard's **Refresh all**, or a workbook's **Run all**) reports what actually happened, since a pre-aggregation rebuild can take longer than the request itself waits for: **Refreshed successfully** once the rebuild is confirmed complete, **Refresh requested** when Cube can't yet confirm whether a rebuild finished, or a message noting the rebuild is still running if it takes more than a few minutes. + ## 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.