Skip to content

Snapshots & Preview ​

The snapshot is the heart of Multiverse: a frozen daily state of all license and usage figures, per portal, customer, and metric.

The rules ​

  • One record per day and portal. If a record already exists for today, it is not written again — no matter how often the snapshot is triggered.
  • Only “today” can be overwritten. The nightly run (and a manual run with the “Overwrite today’s existing preview” checkbox) replaces only today’s record. Historical days are untouchable.
  • The nightly run is the benchmark. A manual snapshot during the day is a preview; the evening job (default 23:00, configurable under Schedules) overwrites it with the final state of the day.
  • Empty results never overwrite a populated state. If a portal suddenly returns nothing during an overwrite, the existing record stays in place. The manual portals are the exception: their figures are Multiverse's own, so an empty snapshot there means the last entry was deleted — and it is recorded.
  • The day is the schedule's day. A snapshot belongs to today in the timezone of the snapshot schedule (Europe/Berlin by default), not to the server's clock — a snapshot forced shortly after midnight no longer lands on, and replaces, the day before.
  • A snapshot is complete or says what is missing. An account a portal could not read that night (a failing API key, an organization without access) is recorded as not read and keeps its last figures in billing; an account that is simply no longer listed is gone. A list that cannot be read to its end fails the portal's snapshot for the night instead of storing a part of it, and a figure that is no number is never stored as 0. What a snapshot has to say about its own figures — a shared tenant split by the users of an earlier read, a mapping that points at nothing — is stored with it and repeated by every invoice run that reads that day.
  • A missed nightly run is caught up. If Multiverse was not running at the scheduled minute, or a manual snapshot was still in progress, the nightly run starts as soon as it can on the same day — also a run that was interrupted by a restart. A run that passes midnight still belongs to, and replaces, the day it started on.

Starting a snapshot ​

ScopeWhereBehavior
All portalsSettings → Snapshots → “Create snapshot now”Dialog closes immediately, progress runs live in the header-bar chip, the result appears as a notification
One portalCamera button in the portal viewas above, but only for this portal

Only one snapshot runs at a time (global lock) — a second start is rejected with a clear message.

Progress & status ​

The chip in the header bar shows the running snapshot live (server push, no polling): which portal is currently being processed, how many are done, and, at the end, a brief result. Failed portals are named — all the others still collect.

Snapshot vs. live ​

Every portal view has a toggle below its search field, in both modes at the same place:

  • Snapshot (default): shows the latest saved state — fast, stable, identical to what trends and billing use. The date switcher also lets you view older days.
  • Load live: queries the portal directly — useful for checking the connection or for an up-to-date view of today. Live data is not saved.

Cleaning up ​

Snapshots can be deleted selectively under Settings → Manage snapshots (everything / one month / one portal / a combination) — e.g. after test runs with wrong credentials.