> ## Documentation Index > Fetch the complete documentation index at: https://docs.reddy.io/llms.txt > Use this file to discover all available pages before exploring further. # Rolling Back a Change > Undo the last change to a simulation through the same guided flow you used to approve it A rollback takes a simulation back to the version before its newest change, whether that change came from a testing round or from the edit wizard. It is not a hidden switch: Reddy first confirms exactly what you want undone, writes a rollback plan, and only applies it after you approve. The next round then tests the result. Rolling back is an approver action. It is available on the newest version only, when no update or edit is in flight and the last change was not itself a rollback. ## Starting a rollback The **Roll back this update** button sits on the newest version on the **Changes** tab. The same action is on the Testing tab's round card as **Roll back the last update**. Changes tab with Roll back this update on the newest version, an edit round Click it and confirm. Nothing changes yet. Roll back this update? dialog explaining that Reddy first confirms what to undo and writes a plan for approval ## Confirming what to undo Reddy opens a review of the change, the same way it reviews a testing round. On the Feedback page, **What Reddy thinks you want undone** lists each part of the change it can take back. Click **Answer the questions** to go on. Feedback page: What Reddy thinks you want undone, listing scenario 4 and a grading note, with an Answer the questions button The wizard asks whether you want the whole change undone or only part of it. Partial rollbacks are ordinary: pick the option that matches, or write your own. Rollback wizard question: undo the whole edit, or keep scenario 4 and restore the original grading ## Approving the rollback plan The rollback plan spells out **what goes back**, **what stays**, and what happens after it ships. Request changes if it is not quite right, or **Apply rollback**. Review the rollback plan: summary, what goes back, what stays, after this ships, with Apply rollback and Request changes Apply this rollback? confirmation dialog Reddy makes the change through the same checks and deploy as any other update. It usually takes one to two hours. ## After the rollback The rollback is a version of its own on the **Changes** tab, with its audit line, plan, report and files changed. The version number goes up, not down: the history keeps every step. See [Versions and Audit Trail](/manual/training/changes-and-versions). Changes tab showing Rollback of edit round 1 as v3 above the edit round v2 and the round 1 update v1 The next round opens on the restored version so testers or trainees play the result. Until another change ships, **Rollback unavailable** shows on the round card: a rollback cannot itself be rolled back. Make the next change an edit. Testing tab after the rollback: version v3 live to trainees, last shipped today, rollback unavailable ## FAQ One step at a time. Rolling back undoes the newest change. To go further, make the next change an edit that describes the state you want; Reddy treats it like any other edit. One of four reasons: an update is in progress, the edit wizard has a change in flight, nothing has shipped yet, or the last change was already a rollback. The round card says which. Yes. The grading rules of the version you are going back to come back with it. Yes. A rollback is a change like any other, so the next round opens on the restored version and testers or trainees play it before anything else ships.