How "go back to yesterday" finds the right version
How a plain-language request to go back to an earlier version turns into one exact version before you're ever asked to confirm anything.
You never need to look up a version code to undo a change to a store. You say what you want in plain words. Reqursor Platform turns that into one exact point in the store's history before it shows you anything to confirm.
How a request resolves
| What you say | How it resolves |
|---|---|
| "Go back to yesterday" | Reqursor Platform finds the most recent version saved before 24 hours ago. |
| "Go back to before the color change" | The AI finds the exact change that altered the design, and picks the version right before it. |
| "Go back to the last update that worked" | Reqursor Platform finds the most recent version that was fully applied to the store, and picks it. |
| "Go back 3 versions" | Reqursor Platform counts back three saved versions in this store's history and picks that one. |
| A specific version you already know | Used exactly as you give it, after a check that it's still valid. |
Always one exact answer before you confirm
Whatever you asked for, by the time you see the preview it is no longer a vague phrase. It is tied to one specific version that can never be changed afterward. You are never asked to confirm something as fuzzy as "roughly yesterday, probably." See Core concepts for why a saved version can never be changed.
Requests to go back to a very old version, or many versions back, get an extra check. If a piece that the version needs is no longer available, Reqursor Platform tells you before you confirm, not partway through the undo.
Why this matters for your agency
- Plain language is enough. You never have to look up or use a version code yourself.
- Nothing unclear reaches your confirmation screen. Whatever you meant by "yesterday" or "before the color change" is turned into one exact answer first.
- Surprises come early, not late. If a version can't be safely restored, you find out before confirming, not after.
Where to go next
Undo: what it restores, and what it doesn't
What actually happens to your store once the version is chosen.
Why you can always get back to a working store
Why getting back after an incident uses this exact same way of finding the right version.
How every change is checked before it goes live
How going back to an earlier version fits into Reqursor Platform's overall approach to keeping your store safe.
How an undo gets triggered
The ways an undo actually starts: suggested by the AI, requested by you, or run across all your stores.
Why you can't undo just part of a change
An undo always goes back to a whole saved version, not just one piece of it, and the new-change alternative when you only need part of an earlier version back.