A stored report never changes

A report is a snapshot, frozen the moment it generates. Every figure and every name in it is captured then and never changes afterwards — even after your live data moves on. This is by design: a report you shared is a fixed record of what was true when you sent it.

Why yesterday's top post can be "missing"

Your live app keeps moving — new posts arrive, badges land, numbers climb. A stored report doesn't follow along.

If last month's report doesn't show a post you saw win yesterday, it's because the post won after that report generated. It'll appear in the next period's report, which reads the window it belongs to. The stored one stays a faithful picture of its own moment.

Names are frozen too

It isn't only numbers — identity is frozen too. Rename a client, a brand or a profile and the reports already generated keep the old name, because that name was baked in when the report was built. The new one appears from the next period's report onward.

Renaming reaches everything in your app, and nothing in a report that already exists. For how renaming and removing work, see editing and removing.

The same holds for the live links your clients are holding. A link opens the exact stored artifact, so a client re-opening an older report still reads the name and figures from when it generated.

One thing is not frozen, and it is deliberate: the language a report is read in. Change a client's language and every report they hold re-words the next time it is opened, live links included. The figures and the AI sentences inside stay exactly as generated — only the words around them move.

The only things you can change

Two controls touch a stored report, and neither alters its content: revoke, which kills the link, and issue new link, which mints a fresh one. Both are about who can open it, never about what it says — see revoking and re-issuing a link.

The figures, the names, the winners, the market log: all permanent from generation.