Restore a published version or an AI draft checkpoint
Published website history and private draft checkpoints are different recovery tools. First identify the affected theme and whether visitors are already seeing the change.
Restore a live version
Ask an authorized Connected AI client to read **theme_history** and show the recorded versions with their theme name, source, publisher, and whether each is restorable. Select the intended restorable version after reviewing the context. A live rollback is a confirmed publishing action, so explicitly approve the chosen version before the client completes it.
The rollback flow snapshots the current live bundle before restoring the selected one. Check the normal public website afterward. Restoring a theme version is not a rollback of customer orders, payments, settings outside that bundle, or the whole workspace database.
Restore an AI draft checkpoint
Before a substantial AI content edit, ask the client to save a named checkpoint for the page, header/footer, or section it is about to change. Later, list the checkpoints and restore the intended content into the same draft target. Other targets and settings remain separate. Sections added after a whole-target checkpoint can remain stored but hidden.
Reuse a section
A workspace section-library preset is an independent reusable copy, not a published version. Updating a preset does not update sections already inserted from it. Use the checkpoint or version appropriate to the problem, then validate and generate a fresh preview before publishing a restored draft.