Troubleshoot the Zoom Logs 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 Zoom Logs connector and how to resolve them.
Zoom access token rejected
Error message:
Zoom access token rejected. Refreshing credentials and retrying.
Cause: Zoom returned an HTTP 401 response. This usually means one of the following: the OAuth credentials are not valid, the app isn't activated, you haven't added the required scopes, or the Zoom user account that owns the app is missing the required role permissions.
Solution:
The connector automatically refreshes credentials and retries. If the error persists across multiple pipeline runs:
- Verify that the Client ID, Client Secret, and Account ID in the Unity Catalog connection match the values on your Zoom app's App Credentials page.
- Confirm that the Zoom app is activated.
- Confirm that the Zoom app has the
report:read:user_activities:adminandreport:read:operation_logs:adminscopes added. - Confirm that the Zoom user account that owns the app has the required role permissions — Usage reports, Admin Activity Logs, and Sign In/Sign Out view permissions. See Required Zoom account permissions.
For details, see Configure authentication to Zoom.
Zoom API rate limit exceeded
Error message:
Rate limit exceeded for Zoom API. Please retry the pipeline after some time.
Cause: Zoom returned an HTTP 429 response. Your Zoom account reached its API rate limit.
Solution:
Wait, then re-run the pipeline. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Zoom OAuth app.
Zoom API temporarily unavailable
Error message:
Zoom API is temporarily unavailable. Please retry the pipeline after some time.
Cause: Zoom returned a transient server error (HTTP 500, 502, 503, or 504).
Solution:
Wait, then re-run the pipeline. If the issue persists, check Zoom's service status.