Troubleshoot the Zip 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 Zip connector and how to resolve them.
Pipeline fails to authenticate (HTTP 401)
Cause: The API key stored in your Unity Catalog connection is not valid. Zip returns status 401 (The provided API key is not valid) when a key is mistyped, expired, or deleted.
Solution:
Verify that the API Token stored in your Unity Catalog connection matches an active key on the API keys tab in Zip. If the key expired or no longer exists, create a key and update the connection. See Configure authentication to Zip and Create a Zip connection.
Pipeline fails with a permissions error (HTTP 403)
Cause: The pipeline ingests a record type that your Restricted API key doesn't grant access to. Zip blocks access to record types left blank in the key configuration.
Solution:
In Zip, edit the restricted key and select at least Read-only access for each record type the pipeline ingests. Alternatively, use a Standard key. See Configure authentication to Zip.
Pipeline is rate limited (HTTP 429)
Cause: Zip limits the API to 150,000 requests per day, per API key. Other applications that share the connector's API key consume the same quota.
Solution:
The connector automatically waits and retries rate-limited requests during a pipeline update. If updates still fail, create a dedicated API key for the connector, reduce the pipeline run frequency, or ingest fewer tables. See Configure authentication to Zip.