Roll back to an earlier Node.js deployment

Check what rollback covers

Deployment rollback rebuilds the selected commit. It uses current environment variables and does not undo database changes. If a newer version changed the database schema, check compatibility with the old code before rolling back. You need website management permissions.

Restore the earlier version

1. Open the website and Deploys. Find the last known working version by commit identifier and time.
2. If you want to prevent the next GitHub push from replacing your rollback, temporarily disable automatic deployment in Settings.
3. Select Roll back for the chosen deployment. The button appears only for eligible deployments.
4. Read the confirmation: the code is fetched again and rebuilt with current settings. Confirm the rollback.
5. Follow its progress and wait for the selected version to become live.

Verify the result

Test the original problem, login and reading and saving data. Check the log for compatibility errors. Fix the problem in the GitHub deployment branch too, so the next deployment does not reintroduce it.

If rollback fails

Wait for any deployment in progress to finish and make sure the application is not stopped. The selected commit must still be available on GitHub. If the button is missing, choose another eligible deployment. To restore the database or a broader service state, follow the backup guide or contact support.