When issues occur during or after rotation, you must decide quickly whether to roll back. The rollback decision matrix provides clear guidance on what action to take based on specific symptoms and ensures fast recovery and minimized downtime, and prevents prolonged service interruptions.

Use this matrix to determine the appropriate rollback action based on observed symptoms:
Symptom Action
Surge in HTTP 401 errors after service account key swap Restore the previous key and reissue tokens
TLS handshake errors for some clients Verify the intermediate CA chain. Revert to the prior certificate if the issue is urgent
Increased latency with no code changes Check token exchange and JWKS network resolution. Revert if the issue persists
Missing operations in tool discovery Compare the OpenAPI specification differences. Roll back if there is a specification regression