The agent changed the hero on your Avada home page an hour ago, and now the client wants the old version back. Builder edits made through this plugin are not in the Changes tab, but each element, template and Library write keeps a WordPress revision when revisions are on, and its response names it as restore_revision_id. That id is the fastest way back. A WPBakery text replace names none, so list the page’s revisions to find the one before it.
If you no longer have the id, the page’s revision history works the same way.
I want the [Home] page (id [5]) back the way it was before [this morning'shero edit].
If you still have the restore_revision_id from that edit, use it. If not, listthe page's revisions with list-revisions, with their dates and who saved them,and help me find the last one before the edit. Show me that revision's contentwith get-revision using content_format raw and with_diff true, and tell me whether thetitle or excerpt differ, since the restore brings those back too.
Wait for my go. Then restore it with restore-revision. Afterwards, read thepage again with the builder's page content tool and include_structure, andconfirm the outline matches the revision. If the restore is refused, tell methe reason it gives.Why this is safe to run
Listing and reading revisions are reads, so you check the exact content you are bringing back, with a diff, before anything changes. The restore itself is reversible: it saves the current live state as a fresh revision first, so a wrong pick is undone by restoring forward to that new point, and nothing in the history is deleted.
For a builder page the plugin adds a check of its own. It refuses a restore when saving the revision as this user would change it or the current page, for example by stripping an element or an embed that user may not keep, and it refuses a revision made with the other builder. After a WPBakery restore the page’s generated CSS is rebuilt, and if that fails the tool says the CSS may be stale.
Restore revision is off until you enable it, is checked against the edit access of the user you bound the agent to, and lands in the Activity Log with the page it changed. For posts and pages without a builder, the general undo a bad edit by restoring a revision recipe covers the same flow.
Already connected? Ask your agent for the “roll back a page builder edit” recipe, name the page and roughly when it went wrong, and it runs the same read-first flow on your own site.