Rolling back a module version

Every version of a module you’ve generated stays available from its version-history sheet (see browsing the modules library), and any of them — not just the latest — can be promoted back to the top. This page covers rolling back to an older version, what changes when it finishes, and when the button won’t let you.

Opening version history

Open the Modules Library and find the module’s card. If it has more than one version, the card shows a button labelled v2, v3, and so on — click it to open the version-history sheet, newest version first.

Rolling back

1. In the version-history sheet, find the version you want back — anything that isn’t already labelled latest.

2. Click Roll back on that version’s row.

3. Confirm in the dialog that appears. It tells you plainly what’s about to happen: your current test environment is replaced with this version, but nothing is deleted — rolling back adds a new version rather than erasing the ones after it.

4. Wait. A rollback reinstalls the module into a fresh sandbox, the same as a full generation, so it can take a few minutes — the dialog stays open and shows Rolling back… until it’s done.

Note

Rolling back doesn’t need the AI agent — it copies the older version’s stored files and reinstalls them directly, so it’s faster and more predictable than re-generating from the requirement.

What changes when it finishes

The version you rolled back to becomes the module’s newest version — one number higher than whatever was latest before, not a rewind of the version counter. It gets its own entry in the version-history sheet, labelled with which version it was rolled back from, and its own download and preview like any other version.

Your sandbox preview is swapped to the freshly reinstalled copy, so previewing in Odoo after a rollback shows the older code, not what you had a moment before. Everything before it in the module’s history — every earlier version, its spec, and its downloads — stays exactly as it was.

When you can’t roll back

• The archive has expired. Versions are only rollback candidates while their ZIP still exists — see downloading a module for the 90-day retention window. Once a version’s archive is gone, its Roll back button is disabled with the same Archive expired (90-day retention) label used for its Download button.
• It’s already the latest. The current latest version has no Roll back button — there’s nothing to promote it to.
• The reinstall fails. If the older version won’t install cleanly into a fresh sandbox, the dialog reports the failure and nothing changes — the module’s latest version stays whatever it was before you clicked. Retrying the same rollback while one is still running can create a duplicate version, so wait for the dialog to resolve (success or failure) before trying again.