Undo a change
Undo a change to your site from the chat or Business → Activity, put it back with Redo, and see what can't be undone.
On this page
Changes to your site's files, and backend-function deploys, can be undone one at a time, whoever made them: Willo's chat, the Growth Engine, an inline text edit, or your own AI agent. Undo needs the editor role or higher.
In the chat
When a turn changes files, Willo's reply ends with a card such as 2 changes made, with Details and Undo. Choose Undo to take back everything that turn changed. Every reply that changed files keeps its card, so you can scroll up and undo an older turn the same way. After undoing the latest turn you can tell Willo why, so it does better next time.
From Activity
- Open Business → Activity. It lists everything that has happened on the business, newest first; Load more goes further back.
- Each chat turn is one row, with the number of files it changed. Choose Undo this change to take back the whole turn.
- To take back only some of a turn, open the row. Each file it changed is listed with its own Undo.
Inline text edits, Growth Engine changes and your AI agent's changes each have their own row. A Growth Engine task also lists its own changes on the task in Business → Roadmap, each with who made it and a Revert. When an undo is done, the row is marked Undone, or Partly undone if only some of its files were.
Put it back with Redo
After you undo a turn or a file, it shows Redo, in the chat and in Activity. Redo puts the change back exactly as it was.
Redo works while nothing has changed those files since the undo. If you undid several changes, redo the most recent undo first. If a file has changed since, Redo says so; ask Willo to make the change again instead.
Some undos have no Redo: backend-function deploys, files over about 200,000 characters or that aren't text, and undos made before Redo was added. For those, ask Willo to make the change again.
When you undo one of Willo's chat changes, Willo is told, so it won't put the change back thinking its edit didn't stick.
What undo does
- An edited file goes back to its previous version. For a very large file (over about 100,000 characters), ask Willo to reverse the change instead.
- A backend function goes back to its previous live version.
- A new file is removed.
- A deleted file comes back if it was a text file under about 100 KB. Large files, images, fonts and other non-text files can't be restored this way, which is why deleting a file asks for approval first.
With drafting off, the site rebuilds with the undo, usually within a few minutes. With drafting on, the undo goes into the draft, and reaches the live site when you publish.
What can't be undone here
Undo covers changes to your site's files and backend-function deploys. Actions that reach outside the site have no undo, which is why they stop for your approval first:
- Emails that were sent.
- Changes to your database rows.
- Publishing or unpublishing a content item.
- Redirects, and changes in Stripe.
Some of these can be reversed with the opposite action, such as unpublishing an item or restoring a Stripe product. Ask Willo, and the approval card says when a change can be reversed.
Going back further
There is no button that restores the whole site to an earlier publish. Version history, beside Publish, is a record of what was published and when. To go back, undo the turns you don't want, or describe the old version to Willo and ask it to restore it. For a backend function a publish replaced, Willo keeps the version live ran before that publish: ask Willo to put it back, and it redeploys that code to your draft for you to publish.
Related: Drafts and publishing, What stops for your approval.