Skip to main content
Last updated on

Troubleshoot Meta Ads ingestion

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

When Meta Ads ingestion in Lakeflow Connect fails, use the connector error class to identify the cause and resolution. The following guidance covers authentication, API limits, access, and Meta service errors.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Authentication failed​

Issue:

You receive an authentication error when creating a connection or running a pipeline.

Resolution:

  1. Confirm that you signed in with a Meta account that has access to the ad accounts you want to ingest from.
  2. When prompted during sign-in, grant all requested permissions (ads_read, ads_management, business_management, pages_read_engagement, pages_show_list).
  3. Reauthorize the connection to complete the sign-in flow again.

Rate limit exceeded​

Issue:

The pipeline fails with META_ADS_RATE_LIMIT_EXCEEDED.

The connector retries rate-limit errors automatically. This error appears when those retries are exhausted.

Resolution:

  1. Wait for your Meta API limits to reset.
  2. Retry the pipeline.
  3. Reduce the number of tables ingested in parallel or reduce the frequency of the pipeline schedule.
  4. If you frequently encounter this error, consider requesting Full Access from Meta (if you aren't using the Databricks-managed OAuth app).

If you contact Meta Support, include the Facebook trace ID from the error message.

Requested data limit exceeded​

Issue:

The pipeline fails with META_ADS_REQUESTED_DATA_LIMIT_EXCEEDED.

Meta returns this error when an API request is too large or complex for its servers to process. This can happen when a request selects many fields or when an Insights report combines a large date range with fields and breakdowns that produce a large result.

Resolution:

  1. Retry the pipeline.
  2. If the error persists for an Insights report, reduce the number of breakdowns or configure a more recent start date.
  3. If you change the parameters of an existing ad_insights table, run a full refresh on the table.

Invalid access​

Issue:

The pipeline fails with META_ADS_INVALID_ACCESS_ERROR.

This error occurs when the requested object doesn't exist, can't be loaded because of missing permissions, or doesn't support the requested operation.

Resolution:

  1. Verify that the object or ad account ID is correct.
  2. Confirm that the authenticating user has access to the requested ad account.
  3. Confirm that the authenticating user granted the required permissions during sign-in, including ads_read and ads_management.
  4. Reauthorize the connection and retry the pipeline.

No accessible ad accounts​

Issue:

The pipeline fails with META_ADS_EMPTY_AD_ACCOUNTS_LIST.

This error occurs when the authenticated user can't access any ad accounts.

Resolution:

  1. In Meta Business Manager, grant the authenticating user access to at least one ad account.
  2. Reauthorize the connection.
  3. Retry the pipeline.

Unconfirmed Meta user account​

Issue:

The pipeline fails with META_ADS_UNCONFIRMED_USER_ERROR.

This error occurs when the Meta user account associated with the access token isn't confirmed.

Resolution:

  1. Complete the required confirmation steps in Meta, such as email or identity verification.
  2. Reauthorize the connection.
  3. Retry the pipeline.

Meta service unavailable​

Issue:

The pipeline fails with META_ADS_SERVICE_UNAVAILABLE_ERROR.

The connector retries recognized transient service errors automatically. This error appears when those retries are exhausted.

Resolution:

  1. Wait and retry the pipeline later.
  2. If the error persists, contact Meta Support and include the Facebook trace ID from the error message.

Insights start date is too old​

Issue:

The pipeline fails with META_ADS_INSIGHTS_START_DATE_TOO_OLD.

This error occurs when the configured Insights start_date is outside the supported historical range.

Resolution:

Set start_date to a more recent date. If you change start_date for an existing ad_insights table, run a full refresh on the table. Otherwise, retry the pipeline. See Start date for the supported range.

Insights parameters changed​

Issue:

The pipeline fails with META_ADS_PARAMETERS_CHANGED.

This error occurs when the parameters for an existing ad_insights table change.

Resolution:

Run a full refresh on the affected table.

Other Meta API errors​

Issue:

The pipeline fails with META_ADS_SOURCE_API_ERROR.

This error occurs when a Meta API response doesn't match a more specific error. The error message includes a Facebook trace ID.

Resolution:

  1. Review the underlying Meta error in the pipeline event log and follow the remediation in Meta's Graph API error handling documentation.
  2. If you contact Meta Support, include the Facebook trace ID from the error message.

Additional resources​

On this page