Version History
Ce contenu n’est pas encore disponible dans votre langue.
Version History
Section titled “Version History”Overview
Section titled “Overview”Version History lists checkpoints created by mutating Sidekick Agent turns, explicit milestones, and legacy migration entries. Ordinary manual edits and read-only Ask/Jury planning do not currently create checkpoints.
Version History is a tenant timeline, not a per-dashboard snapshot or an operational backup. Treat Restore tenant as a tenant-wide administrative operation.
How it works
Section titled “How it works”Expanding a checkpoint shows its captured entity identifiers and a limited pre-change summary. It does not provide a complete visual or field-by-field comparison.
Restoring to a marker sequentially reverts every later checkpoint in the active environment and tenant, newest first. This is also true when the marker was selected from a dashboard-filtered History modal: later checkpoints may include other dashboards and resources. The selected marker itself is not reverted.
The confirmation dialog names the exact environment and tenant. A restore cannot be cancelled after confirmation, is not a cross-document transaction, and can stop after partially applying changes if a request fails or a conflict is detected. Changes made outside the checkpoint timeline are not detected and may be overwritten. Restored documents use merge writes, so a field added after capture may remain if that field did not exist in the captured snapshot.
Step-by-step
Section titled “Step-by-step”- Open Version History.
- Confirm the active environment and tenant.
- Review the timeline of checkpoints.
- Expand a checkpoint to inspect its touched-entity summary.
- Coordinate with other users and verify that every later tenant change may be rewound.
- Select Restore tenant, read the scope warning, and confirm only when the marker is the intended tenant state.
- Wait for completion. If the operation stops, review the reported partial result and refresh affected resources before taking another action.
Common mistakes
Section titled “Common mistakes”Do not restore just because one dashboard looks unfamiliar. The operation is not limited to that dashboard.
Do not use Version History as a substitute for deployment backups, disaster recovery, or a complete audit log. Important environments also need operator-run backups, clear ownership, and change coordination.