Hey @kapa.ai I get two errors on the meta ads connector. One is about reducing the number of fields requested. The other states that the credentials don't have enough permissions, this is strange because I'm certain that the account has full permissions and those were granted to airbyte with the auth flow.

These are two distinct but related issues that have been reported with Facebook/Meta connectors in Airbyte: 1. "Please reduce the amount of data you're asking for" This error occurs when the Facebook Graph API considers the total response data too large. There are two ways to resolve it: • Remove fields via the Schema Tab: Go to your connection's Schema Tab and deselect fields you don't need for the affected stream (

page

,

post

). [Facebook Pages docs] • Reduce page size: Set the Page Size configuration parameter to a lower value (e.g., 25 or 50). This applies to the

post

and

post_insights

streams. [Facebook Pages docs] 2. "Credentials don't have enough permissions" Even if you believe the account has full permissions, this error can occur for a less obvious reason: Facebook only grants the permissions the user actually has on their Page(s), regardless of what Airbyte requests during the OAuth flow. For example, the connector requests these OAuth scopes:

pages_manage_ads, pages_manage_metadata, pages_read_engagement, pages_read_user_content, read_insights, catalog_management

However, users with limited Page roles (e.g., analyst or editor) will not receive

pages_manage_ads

,

pages_manage_metadata

, or

catalog_management

, even if Airbyte requests them. [GitHub issue] Additionally, the

page

stream requests over 100 fields, many of which require elevated permissions. Problematic fields include: •

page_token

,

is_webhooks_subscribed

(require admin access) •

leadgen_tos_*

fields (require lead gen permissions) •

unread_message_count

,

unread_notif_count

,

unseen_message_count

(require messaging/admin access) •

messenger_ads_*

fields,

ad_campaign

,

promotion_eligible

(require ads permissions) [GitHub issue] What you can do: • Verify the actual role the authenticated user has on the Facebook Page — not just the ad account. Even "full" ad account access doesn't necessarily grant all Page-level permissions. • Use the Schema Tab to deselect fields that require elevated permissions you may not have. • If the issue persists, you may need to re-authenticate with a user who has admin-level access to the Page itself. This is a known connector-level issue that has been reported and is being tracked. [GitHub issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai the permissions have been solved. But I still get this error frequently: Please reduce the number of fields requested. Go to the schema tab, select your source, and unselect the fields you do not need. Though this was never an issue before. I've set request page size to 10 and still it fails.

Since reducing the page size hasn't helped, the issue is likely about the number of fields being requested to the Facebook API, not the number of records per page. Here's what you can do: Deselect fields via the Schema Tab Go to your connection's Schema Tab and deselect fields you don't need for the affected streams. This directly reduces the number of fields included in API requests. [Facebook Pages docs] To do this: 1. Toggle a stream to display its fields. 2. Toggle off individual fields you don't need. 3. Click Save changes. 4. When prompted, choose to Refresh the affected streams so the destination data is consistent. [field selection docs] > Note: Deselecting fields will prevent Airbyte from writing them to the destination, but depending on the source, it may still read them. Field selection is only available for top-level fields. Why this might be happening now There is a known bug reported for the

source-facebook-marketing

connector where certain streams (e.g., custom streams using

product_id

as a breakdown) trigger the "Please reduce the amount of data you're asking for" error even on fresh connector setups. The issue appears to be related to how the connector handles the request, not the actual volume of data returned by Meta. [GitHub issue] Additionally, a fix was merged to exclude problematic fields (like

rule

in

CustomAudiences

) that were causing "Too much data was requested in batch" errors — if you're on an older connector version, upgrading might help. [GitHub PR] In summary, the most actionable step right now is to manually deselect unnecessary fields in the Schema Tab for the failing streams. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.