Post-rollback SAML attribute drift after failed Okta upgrade

Goal

Determine whether Okta's automatic rollback restores custom SAML attribute statements and third-party integration configurations when a major version upgrade fails within the two-hour window.

Constraints and uncertainty

Okta documents that in-place upgrades create a pre-upgrade backup and support rollback within two hours. However, the documentation notes that custom org settings and integrations are not automatically restored after rollback. This creates a gap: administrators cannot confirm from the Activity Log alone whether SAML attribute mappings or external identity provider configurations will match the pre-upgrade state once rollback completes.

Questions

1. Does the rollback snapshot capture custom SAML attribute statements, or must they be reapplied manually after every rollback?
2. Are third-party integration tokens and endpoint configurations included in the automatic backup, or do they require separate export before initiating an upgrade?
3. What Activity Log event types definitively indicate that a rollback has restored the full pre-upgrade configuration versus a partial restore?