Usage can’t be verified
This message means Syntic could not check your usage for a moment, so it did not run the request rather than risk charging you wrongly. It is not a usage limit, nothing was charged, and it usually clears within seconds. Wait a moment and try again.
What you may see
| Where | What it looks like |
|---|---|
| API | HTTP 503 with code usage_check_unavailable and the message “Usage can’t be verified right now. Please retry in a moment.” A Retry-After header says how long to wait (usually 5 seconds). |
| Web app | A general notice that the assistant could not respond because of capacity constraints, asking you to try again soon. |
| Syntic Code | A retry with a countdown, or an error telling you to try again. |
Similar messages
These have the same cause and the same fix: something we check before running your request could not be read for a moment.
| Code | Message |
|---|---|
authorization_unavailable | ”Could not verify this credential right now. Retry shortly.” |
plan_check_unavailable | ”The plan could not be verified right now. Retry shortly.” |
What to do
- Wait the number of seconds in
Retry-After, or about five seconds, and send the request again. - If it keeps happening for longer than a few minutes, check status.syntic.ai for an incident.
- If there is no incident and it still fails, contact support with the request ID from the
x-syntic-request-idresponse header and the time it happened.
If you are building on the API
Treat these codes as temporary. Retry after the Retry-After delay with a small random jitter, and stop after a few attempts. Do not show them to your users as “out of credits”. The errors guide has a retry helper.
Related
Was this page helpful?