Help · Pages and the copilot
Undo a change
Where undo lives, what it reverses, and for how long.
Where undo lives
- After the copilot acts. Its receipt carries "Undo"; press it and the receipt reads "Undoing", then "Undone". Or say "undo that". When visitors would see the undo, a card asks "Undo this change?" first.
- In "Activity". Every applied change is listed, and each one that can be undone carries its own Undo.
- In the Composer. "Changes this session" lists your edits with Undo and Redo. It shares one history with the copilot.
- On a published page. Undoing a first publish takes the page offline ("Take it offline"). Undoing a later publish puts the earlier version back ("Put the earlier version back").
- Elsewhere. "Undo this setup" reverses a site setup. Undoing a theme's activation restores the theme you had. Undoing a catalog rebuild restores the previous snapshot. Marking an order shipped, completed or cancelled can each be undone.
How long an undo lasts
- Seven days for draft changes, 24 hours for riskier changes, one hour for administrative changes, and 15 minutes for actions that reach an outside service. A tool can shorten its window, never lengthen it.
- A newer change to the same thing makes an older undo refuse, rather than overwrite what came after it.
Before you approve
- Before you approve, the card tells you whether the change can be undone. A change that is final reads "This can't be undone."
- One-click undo on every change. Coming soon.
- Erasing a visitor's data is final, by design, and its card says so.
In a sentence
Say "undo that" to the copilot. If visitors would see the undo, it asks you to approve it first.
Still stuck?
Email support@amadalis.ai. We aim to reply within one business day; at busy times it can take an extra day. Testers come first: we always give them priority so that they are unblocked.