Skip to main content

History and Rollback

Kvery keeps a version history of each query. Every time a query changes, the previous version is recorded, so you can always see what changed, when, and roll back if needed.

Viewing history​

Open a query's history to see its previous versions in order. This is your audit trail: it shows how a query evolved over time.

Kvery keeps a rolling window of the 100 most recent versions, with older entries dropping off automatically.

Comparing versions (diff)​

Select a history entry to view its diff against the current version. The diff highlights the exact lines of SQL that were added, removed, or changed — making it easy to understand a past change or to find when a bug was introduced.

Rolling back​

If a change caused a problem, roll back to a previous version directly from history. Kvery restores that version as the live query. Because the rollback itself becomes a new history entry, you never lose the ability to move forward again.

How history relates to drafts​

  • Drafts are about staging a change before it goes live.
  • History is about the record of changes that already went live.

A typical flow is: edit as a draft → review the draft diff → publish → (if needed later) open history and roll back. Together they give you a safe, reversible way to evolve queries that other people and systems depend on.

Why this matters​

Queries in Kvery are often production assets — they power API endpoints, scheduled emails, and dashboards. Versioning and rollback mean you can change them confidently, knowing any mistake is one click away from being undone.