Roll Back a Service

Return a service environment to an earlier known release.

A rollback changes the running application version to a previous release. Use it when a recent deployment introduced a regression and the earlier release remains compatible with the current infrastructure and data.

Roll Back

Open the project Manage view.
Select the affected service node and environment.
Confirm the current release and identify the last known healthy release.
Select Rollback and confirm the target offered by StationOps.
Monitor the deploy operation.
Verify health checks, logs, and critical user workflows.

Compatibility Checks

Confirm database changes remain compatible with the older application.
Confirm required environment variables and cloud resources still exist.
Check whether queued messages or stored data use a new format.
Communicate the rollback and preserve the failed release for investigation.

A Rollback Does Not Undo Data Migrations

Application rollback changes the deployed artifact. It does not automatically reverse database migrations, external side effects, or infrastructure revisions.

When the earlier release is no longer compatible, prepare a forward fix instead of forcing a rollback.