History & Restore

Every publish for a flag is captured in a per-flag history log that spans every environment. The History view lives in the flag's sidebar, alongside Variations and Settings, and lets you search, filter, and restore any prior snapshot back to its environment.

History also catches a pending draft that had to be cleared. Starting an environment, pausing it, changing its settings, or scheduling it rewrites the version the pending draft was saved against, so the draft is saved here first and its summary line says which action cleared it. Restore it the same way you restore a publish. See Saving and Publishing for the full list of actions that do it.

The History view of a feature flag: a search box and an All Environments filter above a chronological feed of publish entries, each showing the environment badge, a change summary like '1 rule added, 1 rule deleted', the author, and how long ago it was published. — Every publish, across every environment: searchable, filterable, and restorable.

Opening History

On the flag detail page, click History in the left sidebar under Flag Setup. The middle panel switches to a chronological feed of every publish for this flag. The History entry is only visible to roles that hold the viewFlagDrafts permission.

History used to live in a small History dropdown on the bottom bar. That dropdown was retired: the sidebar entry replaces it and shows entries from every environment in one place, instead of just the current one.

Reading the list

Each row shows a relative timestamp, a small environment tag (e.g. Production or Staging), the publish summary, and the author. Hovering the timestamp shows the absolute publish time. The list is sorted newest-first; older entries can be loaded with the Load more button at the bottom of the list.

The publish summary is a plain count, like "1 rule updated, 1 rule deleted." Only a rule whose content changed counts as updated. Rules that only moved are counted on their own, like "4 rules reordered," and an untouched rule is not counted at all. The count does not say what kind of edit happened to an updated rule: renaming it and retargeting it show up the same way, as "1 rule updated." Declaring a winner leads the line and names it, like "Concluded "Checkout test", winner Answer." Open the entry's detail panel and compare the diff if you need to know exactly what changed.

Filtering and search

Above the list is a filter bar with two controls:

Environment: a multi-select dropdown of every environment that has published history for this flag. Active environments appear under an "Active" group; archived environments appear under an "Archived" group with a muted style. Selecting two or more environments combines them with OR.
Search: plain-text search across the publish summary and the author's name or email. Search runs server-side and updates the list as you type (with a brief debounce).

Filters combine with AND. The Clear filters link appears whenever any filter is set; clicking it resets both the environment selection and the search input.

Archived environments

When an environment is deleted, its history rows are kept and shown in the list with an (archived) suffix on the env tag. Clicking such an entry still opens the detail panel so you can see the publish metadata and summary, but Restore is unavailable: the original environment no longer serves traffic. The button is disabled with an explanatory tooltip and the diff body is replaced by a placeholder.

Viewing a snapshot

Clicking an entry opens a detail panel on the right. The panel shows the publish metadata (summary, author, timestamp, environment) and a change-review diff comparing the historical snapshot against the current published state of that entry's environment. Restore is bound to the same environment: there is no way to pick a different one.

Restoring a snapshot

Click Restore to <env> at the bottom of the detail panel to swap that environment's working draft with the historical snapshot. The button always names the entry's environment: for a Production entry it reads "Restore to Production"; for a Development entry, "Restore to Development".

If the entry's environment already has unsaved draft changes, an inline confirmation prompt asks whether to replace them. Click Confirm restore to overwrite, or close the panel to back out.
On success, you are navigated to that environment's ruleset view so you can review the restored draft and click Publish changes on the bottom bar to make it live. Restoring never publishes automatically.
For entries published to an archived environment, Restore is disabled. There is no path to restore an archived-env snapshot to a different live environment in this release; if you need that flow, recreate the environment first.

Restoring stages a draft. The change is not visible to end users until you click Publish on that environment. The bottom bar shows the restored draft as unsaved changes.

Bookmarking

The history view is URL-tracked. ?section=history opens the History view on page load, and ?section=history&historyId=<id> opens a specific entry's detail panel. You can bookmark or share these URLs.

Retention

The log keeps the most recent publishes per flag, across every environment. The retention cap is configurable via the FLAG_DRAFT_HISTORY_MAX_ENTRIES environment variable on the server.