Skip to content

docs: describe the outcome messages after a manual pre-aggregation refresh #11773

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
keydunov wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −0
Open

docs: describe the outcome messages after a manual pre-aggregation refresh #11773

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs-mintlify/docs/explore-analyze/workbooks/querying-data.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

@claude claude Bot Sep 5, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a single ~90-word sentence that packs the trigger controls, the why, and three outcomes behind one colon. The rest of this section uses bullets for exactly this kind of enumeration, so splitting it reads better and stays scannable:

Suggested change
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.
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 waits for:
- **Refreshed successfully** — the rebuild is confirmed complete.
- **Refresh requested** — Cube can't yet confirm whether the rebuild finished.
- If the rebuild is still running after a few minutes, Cube reports that it's still in progress.

Two smaller things while you're in here:

  • The third outcome is the only one whose message isn't quoted verbatim ("a message noting the rebuild is still running"). If that string is stable in cubejs-enterprise#14657, quoting it in bold like the other two makes the paragraph consistent and lets a reader match what they see in the UI against the docs.
  • Refresh all and Run all aren't described anywhere else in the Cube Cloud docs (only in the Excel/Sheets integration pages, for a different control). Readers hitting this paragraph via the #result-freshness-and-provenance deep link from dashboards/index.mdx:27 may not know those controls. Not blocking, but a short "these controls live at …" clause, or documenting them on the dashboards page, would close the gap.


## 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.
Expand Down
Loading