Updating an environment
When a newer PolicyArc platform version is available, the dashboard shows an Update available badge on the environment. Updating moves that environment's Authorization Server to the current version in place — your configuration, policies, and data are preserved.
What happens
- Backup — before anything changes, we snapshot the environment's tenant database.
- Redeploy — the Authorization Server is restarted on the new version. Database migrations run automatically on startup.
- Health check — the environment is verified healthy on the new version before the update is considered complete.
Downtime
Updating requires a restart, so expect a short outage — typically under a minute — while the Authorization Server redeploys and runs its database migrations.
Automatic rollback
If the new version fails to come up healthy, the update rolls back automatically: the Authorization Server is reverted to its previous version and the database is restored from the pre-update backup, so the environment returns to exactly its prior state. You are never left on a half-applied update.
While it rolls back, the environment is briefly offline (typically a few minutes): the Authorization Server is stopped so its database can be restored safely, then started again on the previous version.
If the rollback cannot complete — for example, the database stays unreachable — the environment is left stopped with its pre-update backup kept, and shows an error. Recover finishes the rollback from that backup. Updates, starts and restarts are refused until it has.
Before you update
- The environment must be running — start a stopped environment first.
- Any in-flight operation (restart or recover) must finish before an update can start.