Troubleshoot the Square 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 Square connector and how to resolve them.
Pipeline fails to authenticate
Cause: Square returned an HTTP 401 or 403 response. This usually means one of the following: the API Token isn't valid, the token expired, or the token isn't authorized for the permissions the connector requires.
Solution:
- Verify that the API Token in the Unity Catalog connection matches a current Production access token in your Square Developer Console.
- Confirm that the token is authorized for the read permissions that the tables you ingest require. See Required OAuth permissions.
To retrieve a new token, see Configure authentication to Square.
Square API rate limit exceeded
Cause: Square returned an HTTP 429 RATE_LIMITED response because the connector sent too many requests in a short period. Square doesn't publicly disclose numeric API rate limits. See the Square error handling reference.
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 Square account.