Regenerate a Saved Report
Saved (pinned) custom analytics reports used to be frozen the moment you saved them — the charts you saw on day one were the charts you’d see a year later, no matter how much the underlying data changed. That’s no longer the case. Every saved report now remembers the question it was built from, and you can re-run that question against current data with one click.
Each report card also tells you, at a glance, how fresh its numbers are — so a stale report can never be mistaken for a live one.
The freshness stamp
Every saved report card shows a line under its title:
Updated 3 hours ago
This “Updated X ago” stamp reflects when the charts on that card were last generated — either when the report was first saved, or the last time it was successfully regenerated. If a card’s stamp is old, the numbers on it are old too.
Regenerating a report
Hover over a report card and a Regenerate button (a circular-arrow icon) appears next to the delete control in the card’s top-right corner. Click it to re-run the report.
Regenerating does not replay stored SQL. Instead, it takes the original question the report was built from and sends it back through the same builder chat used to create custom reports in the first place, running under your own tenant. If that question comes back with a usable chart, the report’s charts and its “Updated” stamp are replaced with the fresh result.
While a report is regenerating, its Regenerate button shows an in-progress state. You can regenerate more than one report at a time — starting a second report’s regeneration doesn’t interrupt the first.
If regeneration fails
Not every re-run succeeds — the underlying question might no longer return usable data, or the request might simply error out. When that happens:
- The report’s existing charts are left exactly as they were.
- The “Updated” stamp is not advanced — it still reflects the last successful run.
- An error message appears directly on the card so you know the attempt failed.
In other words, a failed regeneration never blanks the card and never lets old numbers pass for new ones. You can safely retry once the underlying issue is resolved.
Rate limit
Regenerating a report costs a model conversation plus at least one analytics query, so it’s capped: five regenerations per user per ten minutes. If you hit the limit, wait a few minutes before trying again — reports you haven’t regenerated recently aren’t affected.
Related
- Build custom analytics — how a saved report’s original question is created in the first place
- What is Analytics? — where custom analytics fits alongside dashboards and AI Insights