# Troubleshoot API Key Issues on Confluent Cloud Below are some frequently encountered issues, with information and tips on resolving the issues. ## API key was accidentally deleted #### WARNING When a resource is deleted, associated API keys are also deleted, with the exception of global API keys. The deletion of an API key is a permanent, irreversible action. Before deleting a Confluent Cloud resource, verify that the API key is not in use by any workloads. If the API key is in use elsewhere and the API key is deleted, any other workloads that use the API key fail. To verify if an API key exists, you can use the `confluent api-key list` Confluent CLI command. ## Authentication failure If your client stack trace shows authentication failures, here are some possible causes: * Deleted user account When a user account is deleted, all API keys associated with that account will be deleted. * API key authentication failed If you try to use an API key before propagation completes, authentication failures occur. Depending on workloads, you might need to wait a few minutes more and try again. ## Authorization failure If your client stack trace shows authorization failures, here are some possible causes: * Invalid API Key/Secret * Incorrect permissions or configuration * Scoped to the wrong resource ## Use of new API key before propagation If you try to use an API key before propagation completes, authentication failures occur.