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. To use it, a workspace admin must turn on Lakeflow Connect for SurveyMonkey from the Previews page. See Manage Azure Databricks previews.
Resolve plan limit, authentication, and API rate limit errors from the managed SurveyMonkey connector in Lakeflow Connect.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Pipeline fails with a plan limit error
Error message:
SurveyMonkey returned 402 (plan limit): Basic plans are capped at 25 responses per survey. Upgrade to a paid plan for full response access.
Cause: SurveyMonkey returned an HTTP 402 response because the authorizing account's plan doesn't include access to the requested data. See the SurveyMonkey scopes reference.
Solution:
Confirm that the authorizing SurveyMonkey account has a paid plan that offers direct API access. For plan requirements, see Prerequisites.
Pipeline fails to authenticate
Cause: SurveyMonkey returned an HTTP 401 or 403 response. This usually means one of the following: the client credentials aren't valid, the user revoked the app's access, SurveyMonkey disabled the app after its 90-day draft period, or the app doesn't have the required scopes.
Solution:
- Confirm that the app is deployed as a private app and has the required scopes. See Required OAuth permissions.
- Confirm that the Data Region in the Unity Catalog connection matches the data center that hosts your SurveyMonkey account.
- Update the connection with the current client ID and client secret, then sign in to SurveyMonkey again. See Create a SurveyMonkey connection.
SurveyMonkey API rate limit exceeded
Cause: SurveyMonkey returned an HTTP 429 response because the app exceeded its request limit. Draft and private apps are limited to 120 requests per minute and a daily limit that starts at 500 requests. The daily limit resets at 12:00 AM Greenwich Mean Time (GMT). See the SurveyMonkey request and response limits.
Solution:
When the app reaches the per-minute limit, the connector waits for the limit to reset and retries automatically. When the app reaches the daily limit, the pipeline update fails without advancing the cursor, and the next update resumes from the same point. If this happens repeatedly, reduce the pipeline's schedule frequency, ingest fewer tables, or contact SurveyMonkey to request higher limits for your app.