An extract answers a question at the moment you ask it. But operational data keeps moving. Orders arrive, tickets close, inventory changes, and the table that settled a discussion yesterday may not describe today.
That leaves a familiar choice when someone asks, “Is this still true?” You can ask the question again and lose the table you were looking at, or keep working from an answer you know may be stale. Either way, it becomes harder to explain what changed between the two moments.
Extracts in the current GenViz release give you a third option: refresh the data while keeping the result you already have.
Refresh the original question
Every extract card now has a refresh action in its header, next to the Excel and Parquet download buttons. Click it and GenViz runs the extract’s original query against its original connection. You do not need to reconstruct the question or ask the assistant again.
The refresh icon spins while the query runs. A successful pull flashes a check and becomes a new version alongside the previous one. It never replaces the rows you had. If the query fails, the icon briefly shows an ✗ and the existing history stays untouched.
Move between versions
As soon as an extract has more than one readable version, a pager appears in the card:
◀ VERSION 2 OF 2 ▶
Use the arrows to move through every available version. Hover over an arrow to see the exact date and time of the version it leads to. Hover over the version label to see when the version currently on screen was pulled. Timestamps use an absolute date and time, such as “Aug 26, 2026, 02:15 PM,” localized to the app’s language.
Paging back does more than change a label. The card shows that version’s actual rows, so you can inspect the earlier result and compare it with the fresh pull. If you download an Excel or Parquet file, GenViz downloads the version currently on screen, not the newest version in the background.
A record you can rely on
Each version is an immutable snapshot. Refreshing creates a new extract; it never modifies or replaces an existing one. That makes the history useful for more than checking the latest number. You can return to the exact result that informed an earlier decision, then step forward to see what the same query returns now.
Shared response snapshots follow the same boundary. They stay frozen and are intentionally not refreshable, so a share continues to show exactly what was shared.
Wherever the query runs
Versioned refresh works with databases the desktop app reaches directly and with customer-hosted connector connections. Connector refreshes run inside your network, like every other connector query, so the data still never leaves it.
Coding agents connected through MCP can see version groupings on extracts too. Whether a question starts in chat or from an agent, you can keep the answer you had and check whether it still holds.