Troubleshoot the Marketo connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
Learn how to troubleshoot common issues with the Marketo connector. Each section covers an error the pipeline can surface, its cause, and how to resolve it.
MARKETO_ACCESS_TOKEN_INVALID
Adobe Marketo Engage rejected the connection's access token even after an automatic refresh, so the stored credentials are invalid, expired, or revoked. Edit the connection with a valid custom service client ID and secret from your Adobe Marketo Engage LaunchPoint integration, then rerun the pipeline. See Create a Marketo connection.
MARKETO_ACCESS_DENIED
The Adobe Marketo Engage API user backing the connection lacks permission for the operation in the error. In Adobe Marketo Engage, grant the API-only role the required Access API permission, then rerun the pipeline. See Configure Adobe Marketo Engage.
MARKETO_FEATURE_NOT_AVAILABLE
The object or feature the pipeline is trying to read is not enabled on your Adobe Marketo Engage subscription, such as custom objects or an object synced from a CRM. Contact your Adobe Marketo Engage administrator to enable it, then rerun the pipeline.
MARKETO_TABLE_NOT_SUPPORTED
The requested table isn't available for this connection. Either the name is wrong, or the corresponding activity type or custom object isn't enabled in your Adobe Marketo Engage account. Check the table name in the error, verify the object or activity type is enabled in Adobe Marketo Engage, then rerun the pipeline. For the list of supported tables, see Supported source tables.
MARKETO_JOB_QUEUE_FULL
Adobe Marketo Engage caps its Bulk Extract job queue at 10 jobs, shared across every integration on the subscription, and the connector couldn't get a slot even after retrying. Reduce the number of tables in the pipeline to under 10, check whether other integrations are consuming Bulk Extract slots, then rerun the pipeline.
MARKETO_DAILY_QUOTA_EXCEEDED
Adobe Marketo Engage's daily Bulk Extract export budget is exhausted. The default budget is 500 MB per day, and it resets at 12:00 AM CST. Rerun the pipeline after it resets. If you regularly hit this limit, either sync less data per day by ingesting fewer tables or by narrowing the backfill window with the sync_start_date option, or purchase a higher daily quota from Adobe Marketo Engage to improve ingestion performance and avoid this error.
MARKETO_BULK_JOB_TIMEOUT
A Bulk Extract job didn't finish within the allotted time, usually because of a slow or unusually large source. This error is retryable, so the pipeline retries automatically; rerun it if it doesn't recover. If a single table consistently times out, narrow its backfill window. If it still persists, file a ticket.
MARKETO_TEMPORARILY_UNAVAILABLE
Adobe Marketo Engage temporarily throttled the request because of a rate limit, a daily API call quota, or a busy Bulk Extract queue. This clears on its own and the pipeline retries automatically. No action is needed unless it persists, in which case file a ticket.
MARKETO_INVALID_REQUEST
Adobe Marketo Engage rejected the request as invalid, for example an unknown field or an out-of-range date window. This usually indicates a table or field that Adobe Marketo Engage no longer recognizes. Verify the object and its fields still exist in Adobe Marketo Engage. If they do and the error persists, file a ticket.
MARKETO_MALFORMED_RESPONSE
Adobe Marketo Engage returned a response the connector couldn't parse, usually a transient issue on the Adobe Marketo Engage side. Rerun the pipeline. If it still persists, file a ticket with the details from the error message.
MARKETO_INTERNAL_ERROR
This error indicates an unexpected internal state that isn't user-actionable. File a ticket with the full error message and trace.