Resuming or discarding saved edits

Documentation / Saving, recovery, and troubleshooting

A normal page visit shows live content. When eligible cloud recovery exists, authenticated editors can see Resume saved edits and Discard. The notice identifies saved edits separately so an older draft does not silently replace what visitors see.

Resume the intended draft

Open the correct website, page, and language. Choose Resume saved edits to open the saved revision. The editor uses a revision-specific __draft query parameter; do not copy that query onto unrelated pages or treat it as a public preview link.

If the current tab contains unconfirmed edits, the editor asks before replacing them with saved changes. Preserve any text you still need before accepting. Review the resumed content and any warning that the live page changed after the draft was saved.

After review, use the offered Publish or normal save action. Some recovery states can offer Use saved edits to select a preserved basis; follow the exact warning shown rather than assuming every draft needs that extra step. Changes made by another editor after loading can still block a stale publish.

Discard deliberately

Discard removes the saved recovery edits, not the live page. A confirmation can also cover unsaved changes in the current editor. Check what will be lost before accepting. Discarding a draft is not the same operation as deleting a page backup or reverting a published revision.

Handle interrupted publishing

Finish publishing retries the preserved publish snapshot. It does not substitute later unsaved edits. A pending publish cannot be safely discarded while the original live write may still succeed.

If recovery is absent, check whether cloud autosave is disabled, the page is excluded, or you opened another language. Do not rely on browser storage as a backup. See saving and recovery for page history and site snapshots.