Troubleshoot the Vimeo connector

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Vimeo from the Previews page. See Manage Databricks previews.

Most Vimeo connector errors come from a personal access token that isn't valid or is missing a scope (HTTP 401 or 403), an account without the required Vimeo plan (HTTP 404), or API rate limits (HTTP 429). The following sections explain the cause of each error and how to resolve it.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Pipeline fails to authenticate or lacks permission

Cause: Vimeo returned an HTTP 401 or 403 response. This usually means the personal access token isn't valid or has expired, or the token is missing a required scope. For audit_logs, it can also mean the token doesn't come from an Account Owner or Administrator using an app created on an Enterprise account with audit logs enabled.

Solution:

1. Verify that the Personal Access Token and Account Owner User ID in the Unity Catalog connection match the credentials from the source setup.
2. Verify that the token includes the public, private, and stats scopes. Scopes are fixed when the token is generated, so generate a new token if a scope is missing.
3. To ingest audit_logs, verify that the account is an Enterprise account with audit logs enabled, that the token owner is an Account Owner or Administrator, and that the API app was created on the Enterprise account. If the app was created on another account, create a new app on the Enterprise account and generate a new token from it.

For details, see Configure authentication to Vimeo.

Pipeline fails with HTTP 404

Cause: Vimeo returned an HTTP 404 response for a team or audit log endpoint. This usually means the token's account isn't on a plan with team features, such as a free account. For audit_logs, it can also mean the account isn't an Enterprise account.

Solution:

1. Call GET https://api.vimeo.com/me with the personal access token and check the account field. Team, team member, and team role data need a paid Team or Enterprise plan, and audit_logs needs enterprise.
2. Verify that the Account Owner User ID in the Unity Catalog connection is the team owner's ID. See Find the account owner user ID.
3. To ingest audit_logs, verify that the API app was created on the Enterprise account, then generate a new token from it.

Vimeo API rate limit exceeded

Cause: Vimeo returned an HTTP 429 response because requests exceeded the API rate limit.

Solution:

The connector waits and retries automatically with exponential backoff. If this happens repeatedly, reduce the number of concurrent pipelines that share the same personal access token.

Vimeo API temporarily unavailable

Cause: Vimeo returned a transient server error (HTTP 500, 502, 503, or 504).

Solution:

The connector automatically retries. If the issue persists, wait, then run the pipeline again.