Troubleshoot the Zoho Books 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 Zoho Books connector and how to resolve them.
Zoho access token rejected
Error message:
Zoho access token rejected. Refreshing credentials and retrying.
Cause: Zoho returned an HTTP 401 response. This usually means one of the following: the OAuth credentials aren't valid, the Self Client isn't authorized for the required scopes, or the Region doesn't match your Zoho data center.
Solution:
The connector automatically refreshes credentials and retries. If the error persists across multiple pipeline runs:
- Verify that the Client ID, Client Secret, Organization ID, and Region in the Unity Catalog connection match your Zoho Self Client and organization.
- Confirm that the Self Client is authorized for the required read-only scopes. See Required OAuth scopes.
For details, see Configure authentication to Zoho Books.
Zoho Books API rate limit exceeded
Error message:
Rate limit exceeded for Zoho Books API. Please retry the pipeline after some time.
Cause: Zoho returned an HTTP 429 response. Zoho Books limits the API to 100 requests per minute per organization, and to a per-day call limit that scales with your plan (1,000 calls on Free, up to 10,000 on higher tiers). See the Zoho Books API introduction.
Solution:
The connector waits and retries automatically. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Zoho organization.
Zoho Books API temporarily unavailable
Error message:
Zoho Books API is temporarily unavailable. Please retry the pipeline after some time.
Cause: Zoho returned a transient server error (HTTP 500, 502, 503, or 504).
Solution:
The connector waits and retries automatically. If the issue persists, check Zoho's service status.