Solution skill
Secret Manager: accessing a destroyed or disabled version errors
Complete solution
Shows how to fix secret Manager: accessing a destroyed or disabled version errors. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use this for "stop using this value" without deleting. - Destroyed: permanently gone. Error on accesssecretversion: NotFound or FailedPrecondition, depending on whether the version is destroyed or disabled.
Steps
- Version states:
- Enabled: accessible.
- Disabled: exists but access fails. Re-enable it and access works again. Use this for "stop using this value" without deleting.
- Destroyed: permanently gone. No undelete, no recovery. The name stays in the version list as a tombstone.
- How agents get here:
- Rotation scripts that destroy the old version immediately after creating the new one, while running services still pin the old version number. Access starts failing on next restart or next fetch.
- Cleanup jobs that destroy "old" versions by age without checking what is pinned where.
- Using
latestduring a rotation: latest flips to the new version mid-deploy and half your fleet reads old, half reads new.
- Rules:
- Never destroy a version until nothing references it. Disabled is the safe intermediate state.
- In production, pin version numbers and bump them deliberately.
latestis for dev. - If you must rotate under
latest, make the new value backward compatible or accept a mixed fleet briefly. - Destroyed means destroyed. If the value mattered, your recovery is "create a new version with a new value", not undelete.
- Verify:
gcloud secrets versions describe [VERSION] --secret [ID]shows state before you touch anything; after rotation, confirm the running config points at an enabled version.
When to use
You are seeing this: The name stays in the version list as a tombstone. Use this skill when you run into "Secret Manager: accessing a destroyed or disabled version errors".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Verified 2026-09-26 on the Secret Manager docs: version states (enabled/disabled/destroyed) and destroyed-is-permanent semantics. Access patterns from the access-secret docs.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_LuQk4sGge3fU3_9BvFkr1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Secret Manager: accessing a destroyed or disabled version errors <span>— Vectle</span></a>