The key is still active. Revoking didn't go through. Try again.
Resolve Runner errors for api key creation, copying, and revocation: meaning, safe recovery steps, and how to verify the result.
API key creation, copying, and revocation
Messages you may see
We couldn't create the key. Try again.The key is still active. Revoking didn't go through. Try again.
The create-key error can also appear when copying a newly created key fails. A failed copy does not mean the key was never created. A failed revocation means you must treat the key as active.
- Check whether the new-key dialog already displays a key. If it does, copy it manually into your secure destination rather than creating another key. Never include it in a support report.
- If creation failed before a key appeared, refresh the key list before retrying creation.
- If revocation failed, retry revoking the same key and verify the refreshed list. Contact support if it remains active.
Check: The intended key is listed and securely saved, or the revoked key no longer appears in the active key list.
If the error returns
Contact Support and community after one appropriate retry. Include the exact error, page or conversation URL, workspace/store, approximate time, and what you checked. Remove sign-in codes, credentials, payment details, and customer information.