Rollbacks - Replov Docs
Skip to main content

Rollbacks

Redeploy a previous successful version

Replov keeps deployment records so an authorized project owner or team administrator can select an earlier successful deployment and redeploy it.

Before you start

  • Confirm the target deployment completed successfully.
  • Check whether environment variables or secrets changed after that deployment.
  • Review database migrations for backward compatibility.
  • Plan for a brief service interruption while the prior version is restored.

Roll back from the dashboard

  1. 1

    Open the service

    Select the affected service from its project.

  2. 2

    Open deployment history

    Find the earlier successful deployment you want to restore.

  3. 3

    Start rollback

    Review the selected version and confirm the action.

  4. 4

    Verify the service

    Watch the deployment logs, open the health endpoint, and test a user path.

Database changes are separate
A code rollback does not reverse a database migration or restore deleted data. Apply a tested down migration or restore a database backup separately when the schema is not backward compatible.

After the rollback

Confirm the expected version is running and review recent service logs.

Test authentication, writes, background jobs, and any external integrations affected by the release.

Fix the original issue in a new deployment instead of editing the restored deployment record.