Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

A release broke my app and nobody can put the old version back

Short answer

A rollback needs three things kept ready before every release: the previous version of the code, a backup of the data, and a written step that puts both back. Teams that cannot undo a release usually overwrote the old version or changed the database in a way that cannot be reversed.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • After the last release something important stopped working and the only answer is to fix forward.
  • Nobody knows how to bring the old version back.
  • Releases are done by copying files over the live ones.
  • A release changed the database and the old code no longer works with it.
  • Releases happen late on a Friday and everyone hopes for the best.

Why does this happen?

  1. The old version is overwritten

    When files are copied over the live ones, the previous version is gone unless someone saved it first.

  2. The database changed too

    If a release adds, removes or renames data, the old code can no longer read it. Putting the old code back is not enough.

  3. No one practised it

    A rollback plan that has never been run is a guess. Problems appear only at the moment you need it.

  4. Releases are large

    A release that contains many changes is hard to undo selectively, and nobody can tell which part caused the problem.

  5. No clear trigger to roll back

    Without an agreed sign that says the release failed, the team keeps trying to patch it and the outage gets longer.

What can I do about it today?

  1. Ask what the last good version isAsk your developer which version was running before the problem and whether a copy of it still exists.
  2. Ask for a backup before the next releaseRequest a fresh backup of the data and the current live code just before any release.
  3. Avoid releasing at risky timesChoose a time when the developer is available afterwards, and not just before a weekend or a holiday.
  4. Agree what failure looks likeDecide in advance, for example, that if customers cannot sign in or pay shortly after a release, the team goes back.
  5. Do not attempt to undo it yourselfRestoring files or data without a plan can make it worse. Ask the person who knows the system.

When should I bring someone in?

  • The app is broken right now and nobody can restore it.
  • A release changed the database and you cannot confirm a backup exists.
  • Your agency has no written release steps.

How do I handle it?

  1. Keep every release as its own versionEach release is a named, stored version, so the previous one is always available.
  2. Back up before changingA data backup is taken right before release, and I confirm it can be restored.
  3. Make database changes reversibleChanges are staged so the old code and the new code can both work for a time, or a tested reverse step exists.
  4. Release small and watchSmaller releases are easier to judge and undo, and a short check list is run straight afterwards.
  5. Practise the way backThe rollback is tried on a test copy first, with the steps written down.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

What does rollback mean?

Returning the app and, where needed, its data to the state before a release, because the new version is not working.

Can a mobile app be rolled back?

That depends on the store and the app. Users who already installed an update may not be able to go back, so careful testing before release matters more. I do not make claims about a store's rules here.

Is it better to fix forward?

Sometimes. When the cause is small and clear, a quick fix can be faster. Having a way back means you can choose.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.