Troubleshoot the Verkada 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 Verkada connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Verkada rejects the access token
Error message:
Verkada access token rejected. Refreshing credentials and retrying.
Cause: The API key stored in the Unity Catalog connection is not valid, has expired, has been rotated, or was created for a different region than your organization.
Solution:
Verify that the API Key and Data Region in the Unity Catalog connection match your Verkada organization. The connector refreshes the short-lived token automatically, so a persistent failure points to the API key. If the key was rotated, create a new key and update the connection. See Configure authentication to Verkada and Create a Verkada connection.
The pipeline fails with a permissions error
Cause: The API key lacks Read-only access to the product a table reads — Core for audit_log, or Access Control for users. Verkada API key permissions cannot be edited after the key is created.
Solution:
Create a new API key with Read-only access to the required products, then update the Unity Catalog connection. See Configure Verkada.
Requests are rate limited
Cause: Verkada limits the API to 300 requests per minute per organization and returns 429 Too Many Requests when the limit is exceeded.
Solution:
The connector honors the Retry-After header and retries automatically with exponential backoff, so rate limiting is usually transient. If it persists, avoid running multiple pipelines against the same Verkada organization at the same time.