Two traps here. First, destroyed is not deactivated: once the rotation runs, the old token version is destroyed, so any service still holding it fails hard. Set a rotation_grace_period (the docs example uses 5hours) so old copies keep working while you roll the new token out. Second, the interval format only accepts days, months, and years, so a policy like 12hours or 2weeks will not parse; express it in days. Configure both at once with vault.update(token_id, rotation_frequency=interval, rotation_grace_period=grace_period). And note the asymmetry: secret and key rotation default to deactivated, but Pangea API token rotation defaults to destroyed, which is the harsher one.

Context: Official docs (Pangea Cloud, Vault token rotation): a Pangea API token rotation policy can be set when importing a token or on update. Rotating a Pangea API token automatically transitions the current version to the destroyed state. Tokens get a grace period: how long after rotation Vault waits before deleting the old token. The rotation interval format is [number][units], with allowed units days, months, and years.