Analyticsbeginner

Regenerate a Saved Report

Saved custom analytics reports used to be frozen snapshots. Now each report card shows how old its numbers are and offers a Regenerate control that re-runs the report's original question against current data.

3 min read

Regenerate a Saved Report

Saved 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

Charts on a saved report card show when their numbers were last generated:

Updated 3 hours ago

This “Updated X ago” stamp is tracked per chart, not once for the whole card. A chart’s stamp reflects when that chart was first saved, or the last time that chart was successfully refreshed or regenerated.

That means different charts on the same saved report card can show different freshness times. For example, a snapshot chart keeps its original saved date even if another live chart on the same card refreshes later. On a mixed card, check each chart’s freshness stamp to understand how current that chart’s numbers are.

Regenerating a report

Hover over a report card and a circular-arrow button appears in the card header, next to the three-dots menu. It has no visible text — hovering it shows either Get the latest numbers or Rebuild this card with the latest numbers, and which one you get tells you what kind of chart you are looking at:

  • A live chart — one that still carries its own query — gets the refresh action. It simply re-runs that query.
  • A snapshot chart gets the rebuild action, which is the regeneration this article is about. It is offered only to the owner of the report tab, so someone reading a report shared with them will not see it on snapshot charts.

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 usable charts, the report’s charts and their “Updated” stamps are replaced with the fresh result.

Live charts may also be re-measured automatically when you view the saved report under a different date range. When that refresh succeeds, the affected live chart updates its data and freshness stamp. Snapshot charts keep their own saved data and saved date unless they are successfully regenerated.

While a report is regenerating, the 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.

There is also a Refresh button in the report header, tooltipped Get the latest numbers for every card here, which re-runs every live card on the tab at once.

If regeneration fails

Not every re-run succeeds — the underlying question might no longer return usable data, or the request might simply error out. Automatic refreshes can fail too. When that happens:

  • The affected chart’s existing data is left exactly as it was.
  • The chart’s “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 refresh or regeneration never blanks the chart 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.

Tags

How To
Back to Analytics