Troubleshoot the Celigo 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 Celigo connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Pipeline fails to authenticate
Cause: The API token is not valid, has been revoked, or lacks access to the audit log API. Celigo returns HTTP 401 or 403, and the connector fails the pipeline as a configuration error.
Solution:
Regenerate a full-access API token in integrator.io and update the connection. See Configure authentication to Celigo for token steps and Create a Celigo connection for updating credentials. Confirm the connection's Data Region matches the account that issued the token.
Pipeline is rate limited
Cause: Celigo throttles the integrator.io API and returns HTTP 429. The connector honors the Retry-After header and retries automatically, so transient throttling resolves on its own. A pipeline fails only when throttling is sustained across retries.
For Celigo's published API request limits and per-page response-size cap, see Celigo's API pagination documentation.
Solution:
Reduce the ingestion frequency of the pipeline so runs overlap less with other integrator.io API traffic. See Common pipeline maintenance tasks to adjust the schedule.
Pipeline fails with a request error
Cause: Celigo rejects the request time range or cursor and returns HTTP 422. This usually means the start_datetime connector option is not a valid ISO-8601 UTC datetime.
Solution:
Set start_datetime to an ISO-8601 UTC value, such as 2026-01-01T00:00:00.000Z, or remove it to use the default 365-day backfill. See Connector options.