Troubleshoot the Glean 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 Glean connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Pipeline fails to authenticate
Cause: Glean returned an HTTP 401 or an HTTP 403 response that isn't a rate-limit response. This usually means the API token is invalid, the token doesn't carry the scope for the table being ingested, or the Subdomain doesn't match the deployment that issued the token. The connector treats this as a configuration error and fails the pipeline.
Solution:
- Confirm that the API Token in the Unity Catalog connection is valid and hasn't been revoked.
- Confirm that the token carries both the Insights and Shortcuts scopes. A token missing a scope fails only for the table that needs it.
- Confirm that the Subdomain in the Unity Catalog connection matches the deployment that issued the token.
For details, see Configure authentication to Glean.
Glean API rate limit exceeded
Cause: Glean returned an HTTP 429 response because the connector sent too many requests in a short period.
Solution:
The connector honors the Retry-After response header, then falls back to exponential backoff and retries automatically. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Glean deployment.
Glean API temporarily unavailable
Cause: Glean returned a transient server error (HTTP 500, 502, 503, or 504).
Solution:
The connector automatically retries with exponential backoff. If the issue persists, wait, then run the pipeline again.