<![CDATA[Topics tagged with rollback]]>https://fusionauth.io/community/forum/tags/rollbackRSS for NodeTue, 29 Sep 2026 04:46:02 GMTInvalid Date60<![CDATA[How does rollback work for FusionAuth Cloud after a major version upgrade?]]>For FusionAuth Cloud deployments, the rollback process must be handled by FusionAuth support—it is not something you can perform yourself.

Plan Eligibility and Backup Retention Business and High Availability (HA) Deployments: Upgrade backups are retained and available for 30 days Basic Deployments: Backups are not included, so rollbacks cannot be performed How to Request a Rollback

If you identify an issue after performing the upgrade:

Open a support ticket with FusionAuth The support team will perform the complete database rollback for you Expected Downtime

The rollback operation typically takes 20 minutes to 2 hours, depending on:

Database size How quickly the operations team can complete the rollback

Note that this involves a complete database rollback, so plan for 1-2 hours of downtime.

Support During Upgrades

For production upgrades, FusionAuth can provide:

An engineer on standby during your scheduled upgrade window An on-call support number for emergency assistance Pre-Upgrade Best Practices

Before upgrading to 1.69.1:

Review Release Notes for breaking changes, database migrations, and API modifications Choose an Upgrade Strategy: Incremental (version-by-version) for lower risk Direct upgrade for speed (but requires thorough testing) Test in Staging to verify: Authentication flows, webhooks, and APIs function correctly Templates render properly Database migrations complete successfully Coordinate with Support to schedule the upgrade and have assistance available if needed ]]>https://fusionauth.io/community/forum/topic/3156/how-does-rollback-work-for-fusionauth-cloud-after-a-major-version-upgradehttps://fusionauth.io/community/forum/topic/3156/how-does-rollback-work-for-fusionauth-cloud-after-a-major-version-upgradeInvalid Date