Troubleshoot the OpenAI connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page describes common errors you might encounter with the managed OpenAI connector and how to resolve them.
Pipeline fails to authenticate
Cause: OpenAI returned an HTTP 401 or 403 response. This usually means one of the following: the Admin API key is not valid, the key was revoked, or the key is a project or service-account key rather than an organization Admin API key with the required read scopes.
Solution:
- Confirm that the Admin API Key in the Unity Catalog connection matches a current, active key on the OpenAI organization's Admin keys page.
- Confirm that the key is an organization Admin API key, not a project API key or a service-account key. The Admin API endpoints require an organization-level key.
- Confirm that the key has the read scopes the connector requires. See Configure authentication to OpenAI.
If the key was rotated, update the connection with the new key. See Create an OpenAI connection.
Pipeline is rate limited
Cause: OpenAI returned an HTTP 429 response. The organization reached its Admin API rate limit.
Solution: The connector waits and retries automatically. If the error persists across multiple pipeline runs, reduce the pipeline's schedule frequency, or reduce the number of concurrent pipelines that share the same OpenAI Admin API key.
OpenAI API temporarily unavailable
Cause: OpenAI returned a transient server error (HTTP 500, 502, 503, or 504).
Solution: The connector retries automatically with backoff. If the issue persists, check OpenAI's service status, then re-run the pipeline.