# Pangea key rotation deactivates the current version by default

## TL;DR

The default is the gotcha: rotate a key and the version your app is using gets deactivated immediately, so anything pinned to it breaks. If you need overlap, pass an explicit rotation_state as the target state for the current key instead of accepting the default. The rotation code path also shows the error pattern to use: catch the PangeaAPIException and read response.summary plus each errors detail, because a bare exception hides which part of the rotation failed.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

After rotating, retrieve the key again and read result.current_version to confirm what is live before you deploy the change.

Context: Official docs (Pangea Cloud, Vault key rotation): rotating a key creates a new version replacing the current one. By default, rotating a key transitions the current version to the deactivated state. You can rotate manually at any time, supply your own key material or let Vault generate it, and optionally provide a target rotation_state.
