database_not_configured means the service has no data store configured for the route you called. Read this page when a keys, usage, quota or billing route answers with this code.
What happened
Routes: the keys routes (/v1/keys*), the usage routes (/v1/usage* and /v1/quota), and the billing routes (/v1/billing*).
These routes read and write stored records. When no data store is configured, they refuse every request with this code, after the credential and scope checks pass. So a 403 scope_denied still comes first when your key lacks the scope.
The runs routes report the same condition as not_configured.
How to fix
- Retry after a few minutes. It is a service-side configuration problem, and a fast retry loop gets the same answer.
- Nothing was written, so a retry of a
POST,PUTorDELETEcannot apply twice. - If it persists, report the
request_id.
Example
Related
- Error handling - a status-to-action table and a retry helper for every error.
- Request ids - send your own
x-request-idand quote it when you report a problem. - not_configured - the same condition on the runs routes.
- auth_not_configured - what API-key callers see first when no database is configured.
- Problem codes - every code, its status, and whether a retry can help.