Reviewing changes and recovering earlier versions

Documentation / Agentic editing and connections

Review the saved result, not only the assistant's description. Ordinary page-update tools change the page immediately and do not read, save, or publish editor cloud drafts. Keep a note of the target page ID, language, and approved scope before a substantial change.

Review a completed edit

Ask the assistant to read the page back, identify the changed fields, and report its current revision. Open the rendered route yourself. Check headings, links, images, mobile layout, availability, and the selected language. For template-bound pages, verify editable areas and locked content separately.

A successful write does not prove that the visual result or wording is correct. Conversely, an error during a multi-file change does not always mean nothing was written. Review partial-operation details before retrying.

Recover page content

Use list_page_revisions to locate a suitable page/language snapshot, then get_page_revision to inspect it. These tools read history; they do not restore it automatically. After approval, an assistant can apply selected content fields through a normal update against the current page version. Preserve current identity, route, root, and language unless changing them is explicitly intended.

The CMS Backups tab also provides Preview and Restore. Review the confirmation before restoring a full backup, since that action is broader than copying one paragraph.

Keep recovery types separate

Resume saved edits concerns unpublished editor cloud drafts. Custom design has its own reviewed scope and video drafts. Shared-shell history restores a revision into a new draft and requires separate publication and activation. A site snapshot captures wider site JSON and needs administrator-assisted recovery.

Choose the narrowest recovery that covers the damage. See saving and recovery before restoring shared design or site-wide content.