Skip to content
Governance Platform

Rollback

Rollback restores the platform to a previous approved release when an upgrade cannot be accepted. Plan rollback before upgrading.

Before Rolling Back

Section titled “Before Rolling Back”

Confirm whether the failed upgrade changed platform data. Some data migrations may not be automatically reversible. If the release notes identify non-reversible changes, follow the release-specific recovery plan.

Rollback Flow

Section titled “Rollback Flow”
  1. Stop or pause affected user workflows if required by the incident plan.
  2. Restore the previous chart version and values.
  3. Restore data from backups if the release-specific plan requires it.
  4. Verify sign-in, project access, attachments, reports, indicators, lineage, and certificates.
  5. Record the incident, release versions, evidence, and customer decision.

Support Notes

Section titled “Support Notes”

Keep the release manifest, previous values, current values, and validation evidence with the support record. Do not continue retrying an upgrade until the rollback cause is understood.