If a build did something you did not want, you can put your app's code back to an earlier point. Nothing is erased, and you can undo the rollback.
4 min readUpdated October 3, 2026
Who can roll back
The app's owner and anyone on its project can roll back.
Roll back
Find the build you want to undo. You can start from its proof card in chat (choose Roll back app… from the message menu; on a phone it is under More actions), or from the Runs list in the app panel (tap Roll back…).
Choose a point. Go back to before this run undoes this build and everything after it. Go back to right after this run keeps this build and undoes everything after it.
Read the lists. The window names every build that will leave the app and any that will come back.
Tap Roll back.
From the Runs list: choose a point and read which builds will leave the app.
Or start from the proof card: Roll back app is in its message menu (under More actions on a phone).
Your preview rebuilds with the older code. In Stacks, the undone bullets show Rolled back, and approving one again builds it fresh.
Roll back, or ask for a change?
If a build mostly worked and needs adjusting, a new bullet that describes the fix is usually quicker. Roll back when a build went in the wrong direction, or when later work depends on getting back to a known good point first.
Undo a rollback
The app panel's Runs list shows a short line saying what was rolled back, with an Undo link. Tapping it brings the code back exactly as it was.
What a rollback does not change
Only the app's code changes. Changes a build made to your app's database stay as they are.
If a build is running on the app when you roll back, it lands on top of the rolled-back code when it finishes.
Your Live app does not change until you press Update Live.
If a build finishes while the rollback window is open, Co-Create refuses the rollback rather than undo work you have not seen. Open it again to see the new list.