Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.
This page describes common errors you might encounter with the managed Anaplan connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Anaplan rejects the access token
Error message:
Anaplan access token rejected. Refreshing credentials and retrying.
Cause: The CA certificate or private key stored in the Unity Catalog connection is not valid, no longer matches the certificate registered with the Anaplan account, or has been rotated.
Solution:
Verify that the Certificate (PEM) and Private Key (PEM) in the Unity Catalog connection match the certificate registered with your Anaplan account. The connector obtains and refreshes the short-lived access token automatically, so a persistent failure points to the stored certificate or key. If either was rotated, update the connection. See Configure authentication to Anaplan and Create a Anaplan connection.
The pipeline fails with a permissions error
Cause: The Anaplan account behind the CA certificate lacks the required roles. The audit events API requires the Tenant Auditor role with Audit enabled for the tenant, and the users API requires administrative access to the tenant's users.
Solution:
Confirm that Audit is enabled for your tenant and that the account behind the certificate has the Tenant Auditor role and administrative access to read users. A Tenant Administrator can enable Audit and assign roles. Then update the account or certificate and update the Unity Catalog connection. See Audit and Configure Anaplan.
Requests are rate limited
Cause: Anaplan enforces a tenant-wide Integration API rate limit of 600 requests per minute (about 10 requests per second) across all workspaces, and returns 429 Too Many Requests when it is exceeded. See Model busy behavior and retry strategy.
Solution:
The connector honors the Retry-After header and retries automatically with exponential backoff, so rate limiting is usually transient. Anaplan recommends a 10-second wait before retrying. If it persists, avoid running multiple pipelines against the same Anaplan account at the same time, because the limit is shared across the whole tenant.