Troubleshoot the Asana connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Asana from the Previews page. See Manage Databricks previews.
Resolve connection sign-in, authentication, rate limit, missing data, and No matching route errors from the managed Asana connector in Lakeflow Connect.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Connection sign-in fails
Cause: The client ID or client secret is not valid, the redirect URL doesn't match your workspace, or the app isn't available in your Asana workspace.
Solution:
Verify that the Client ID and Client Secret in the connection match your Asana OAuth app. Confirm that the app's redirect URL is https://<workspace-url>/login/oauth/http.html, that the app has Full permissions enabled, and that the app is distributed to your workspace. See Configure authentication to Asana.
Pipeline fails to authenticate
Cause: Asana returned an HTTP 401 response after the connector refreshed the access token. The authorizing user might have revoked the app's access, or the user might no longer be active in Asana.
Solution:
The connector refreshes access tokens automatically. If authentication still fails, sign in again from the connection so that an active Asana user reauthorizes the app. See Create an Asana connection.
Pipeline is rate limited
Cause: Asana returned an HTTP 429 response because the connection exceeded the Asana rate limits. See Asana rate limits.
Solution:
The connector waits for the interval in the Retry-After response header and retries automatically. If rate limiting persists, reduce how often the pipeline runs or the number of pipelines that share the same connection.
A table is empty or is missing records
Cause: The connector skips requests that Asana rejects with HTTP 402, 403, 404, or 451 responses. Asana returns these when the authorizing user can't access an object, or when a feature isn't included in your plan.
Solution:
Confirm that the authorizing user can view the missing objects in Asana. To ingest portfolios, goals, and time tracking entries, confirm that your organization has an Advanced or Enterprise plan. For other coverage limits, see Asana connector limitations.
Pipeline fails with a No matching route error
Cause: Asana returned an HTTP 404 response with an error message that contains No matching route. This means that Asana doesn't recognize the API endpoint that the connector called.
Solution:
Retry the pipeline update. If the error persists, contact your Databricks account team.