Problems & solutions
“Recording kept” means you can retry the pending recording. It is not a permanent archive: do not cancel it if you still need that audio.
No API credit · recording kept
The provider explicitly reports exhausted credit. Check the account or team used by your key, add credit in Billing, then return and retry. This is not an internet failure.
API quota unavailable · recording kept
The response does not establish that your balance is zero. Check billing activation, available credit, project quotas and the account associated with the key. Do not add money blindly.
Billing limit reached · recording kept
A billing cap was reached. Check Billing and the applicable limits. If you choose to raise a cap, review your budget first; adding credit alone may not remove the cap.
API limit reached · recording kept
An organization or project spending/usage limit was reached. Check the limit shown by your provider. Raise an allowed spending limit or wait for its reset; a provider-approved usage limit may require a request for an increase.
Too many requests
Wait briefly, then retry. This usually concerns request or token throughput, not your balance. Repeated attempts can prolong the problem.
Invalid API key / API access denied
Check that the provider matches the key, that it has not expired or been revoked, and that the required models are allowed. Replace a compromised key in the provider console and in the app.
Not sent / internet or timeout error
Check Wi-Fi or mobile data and any VPN. For a transient provider outage, wait and retry. If the app says “recording kept”, retry before cancelling; cancelling discards that pending recording.
The AI provider returned no text.
The response contains no transcription; this does not prove a credit problem. Make sure microphone access is allowed, speak after recording begins, and try a short sentence. Quiet or empty audio does not require extra credit.
Provider error / model unavailable
Try again later for a temporary outage. If a model is unavailable or access is denied, check the provider and key permissions. Contact support with the app version and error code, not your key or dictated content.