Revert the setup to a checkpoint

A revert returns the whole workspace setup to a checkpoint or an earlier moment, as a new revision. You need the Editor, Admin, or Owner role; to revert a change of the workspace name, logo, or favicon, you need the Admin or Owner role. What a revert restores and keeps is under Reverts.

Related pages: activity history and checkpoints, CLI reference, resolve conflicts.

Revert in Setup

1. Open Setup → Activity history and find the checkpoint. Switch the view to Checkpoints only to see just checkpoints. To include daily ones, pick All checkpoints in the list of checkpoint kinds next to it, which shows Important checkpoints by default.
2. Open the checkpoint’s ⋯ menu and select Revert to this checkpoint.
3. If the revert recreates an MC252 that was deleted since, the dialog lists it first. Press R on each listed device, or type the code from its screen. Each one shows Confirmed once it is.
4. Read the list of what the revert creates, changes and deletes.
5. Select Revert. It turns on once every listed device is confirmed.

Revert from the CLI or the assistant

pnpm hmi checkpoint revert <checkpoint-uuid> --dry-run
pnpm hmi checkpoint revert <checkpoint-uuid>
pnpm hmi checkpoint revert --at "2026-10-09 14:30:00"

1. Run the revert with --dry-run to list the changes without making them.
2. Run it again without --dry-run. To revert to a moment instead of a checkpoint, use --at with a local time.
3. If the command asks, press R on each recreated MC252, or type the code from its screen.

To use the assistant instead, ask it to revert and review the summary it shows before you allow it. If the revert recreates an MC252, revert in Setup or the CLI: the assistant cannot confirm devices.

After the revert

1. If you reverted by mistake, revert to the Before revert checkpoint that the revert took.
2. If the revert changed the programs of an MC252 with Deploy on save off, select Sync now on its Programs tab, as described in Deploy programs to an MC252.
3. In each local checkout, run hmi pull. Settle the conflicts it reports with hmi resolve.

When a revert fails

Message	What to do
The setup changed since you opened this	Open the revert again and review the new list
Setup history does not reach that far back	Choose a later moment or a checkpoint
Some files are no longer stored	Choose another checkpoint; that setup’s files cannot be restored
Confirm every deleted device on site	Revert in Setup or a terminal and confirm each listed MC252
The PIN now belongs to another device	Choose another checkpoint; that connection cannot be restored
Some items can no longer be read	Choose another checkpoint

If the message names an item that would no longer be valid, such as an automation over a lowered automation limit, fix the item or choose another checkpoint.