Roll back a release

If a release has gone wrong, you can put back the version that was running before it. Rolling back puts back the code, and your data stays as it is, unless you choose to put the data back as well.

Roll back a release

1. Open Releases.
2. On the production card, open Go back to an earlier version.
3. Read the button, which names the version you'd go back to, for example Roll back to 0.4.0.
4. Decide about your data (see below). By default the box is not ticked, and only the code goes back.
5. Type prod in the box. Capital letters are fine.
6. Press Roll back to 0.4.0.

The screen confirms it is queued, and says whether it is "code only — the data stays as it is" or "code and data". It happens on the next run, and shows in History like a release.

Only an owner or an admin can roll back production. A test copy has its own Roll back button on its card: an editor can use it too, it is a click with nothing to type, and it only ever touches that test copy.

Code only, or the data too

Rolling back is code only unless you tick the box. Your records stay exactly as they are, including everything added since the release. That is usually what you want, because your staff and customers have kept working since.

Where the release you're undoing changed your existing data, Divvent made a restore point of the data just before it. Only then is there a second choice, a box that reads like this:

The age is worked out when you open the page. Tick it only if you really want your data as it was at that moment: every record added, changed or removed since then is lost, and that can't be undone. If a release only added things, for example a new field, no restore point was needed and the box isn't shown. Only the code goes back.

When the data has to go back too

Sometimes a release changes your data in a way the older version can't work with. Then the box is already ticked, you can't untick it, and a sentence under it says which changes made that so. If you don't want to lose what has changed since, don't roll back. Fix the problem with a new change and release that instead.

How far back you can go

• One release. Rolling back undoes the last release, and only that. Once you've rolled back, there is nothing further to go back to. The card says which rollback it is sitting on, and releasing a version moves it on again.
• 30 days. You can go back to an earlier version, and put the data back too if you choose, for 30 days after a release. This is the limit of how long your data's history is kept, and it can't be extended.
• Further back than that, use a backup. Backups are taken every night and kept for a year by default. See Backups and restoring your data.

If the button isn't there, the card says why instead. Nothing may have been released yet, or no release has replaced another one yet, or a release is already on its way.

What can't be rolled back

An urgent platform update. Divvent sometimes applies an urgent update, such as a security fix, to every application straight away. Rolling back past one would bring back what it fixed. So if going back would put back a version from before an urgent update, the card says so, and only our team can roll it back. Ask us and we'll look at it with you. See Platform updates.

A standard platform update doesn't get in the way. Roll back after one still undoes your own last change, back to the version it replaced.

Rolling back your data without changing the version

If the version is fine but something went wrong with your data, for example records deleted by mistake, you don't need to roll back a release. Restore a backup or a moment from the last 30 days instead, from Settings, then Backups. See Backups and restoring your data.