@kapa.ai 2026-03-12 094714 source WARN Facebook API Utilization is too high (85)%, pausing for 00200

This warning means the Facebook source connector has detected that your Facebook API rate limit utilization is high (85%), so it is intentionally pausing requests for 2 minutes to avoid hitting Facebook’s limits. A very similar behavior is described in a forum thread where the logs repeatedly show “Utilization is too high … pausing,” and the root cause was that the Facebook API utilization in the Facebook dashboard had reached 100%. [Facebook sync issue] To address it: 1. Check your Facebook app’s API utilization and rate limits in the Facebook developer dashboard. 2. If you’re consistently near 100%, request higher quota / advanced access from Facebook as suggested in that thread. [Facebook sync issue] 3. Ensure you’re using a long‑lived Page token, as Facebook heavily throttles default tokens and this can make syncs very slow due to rate limiting. [Facebook Pages perf] Airbyte is behaving as designed here: it pauses when rate limits are close to being hit, then resumes once it’s safe to continue. 👍 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 what is the use of using long lived token

Based on the previous conversation context (Facebook API rate limiting), using a long-lived token with the Facebook Pages connector in Airbyte serves this key purpose: Avoiding heavy rate limiting. Facebook heavily throttles API tokens generated from standard Facebook Apps by default, making it infeasible to use such a token for syncs with Airbyte. Without a long-lived token, your syncs could take days due to rate limiting. [Facebook Pages perf] In practical terms, this means: • Syncs complete in a reasonable time rather than being constantly paused. • You're less likely to see the "Utilization is too high, pausing" warnings you encountered. To generate one, you need to follow the steps to create a Long-Lived Page Token via the Facebook developer tools, as outlined in the Facebook Pages setup guide. [Facebook Pages] 👍 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 but until yestrday it was working i was using it for months

That's a valid observation. Based on the knowledge sources, there are a couple of documented reasons why a previously working Facebook connection might suddenly start hitting rate limits: 1. Undocumented API changes by Meta. A GitHub issue reports users suddenly seeing rate limiting errors from Facebook/Meta that started "just in the last few days" without any changes on their end — suggesting Meta may make undocumented rate limit changes. [GitHub issue] 2. Internal Server Errors from Facebook's side. Another GitHub issue documents a Facebook Pages connector that worked for months and then suddenly started failing, with the root cause being an error from Facebook's API itself — not anything changed in Airbyte or the connector configuration. [GitHub issue] So the sudden change in behavior is likely on Facebook/Meta's side, not something you changed. Unfortunately, the knowledge sources don't provide a definitive fix for this scenario beyond: • Checking your Facebook app's API utilization in the Facebook developer dashboard. • Requesting a quota upgrade from Facebook if needed. [Facebook Pages perf] If the issue persists, it may be worth reaching out to Airbyte support or checking the Airbyte community forum for others experiencing the same sudden change. 👍 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 x-ad-api-version-warning The call has been auto-upgraded to v23.0 as v19.0 has been deprecated. x-business-use-case-usage {"5997471":[{"type":"ads_insights","call_count":1,"total_cputime":46,"total_time":82,"estimated_time_to_regain_access":0,"ads_api_access_tier":"development_access"}]} x-fb-ads-insights-throttle {"app_id_util_pct":0.01,"acc_id_util_pct":0,"ads_api_access_tier":"development_access"}

The response headers you're seeing reveal two important things: 1. API Version Auto-Upgrade Warning The header

x-ad-api-version-warning

shows your connector was calling the deprecated v19.0 of the Facebook Marketing API, which was automatically upgraded to v23.0 by Meta. This is a known issue — v19.0 was deprecated on February 4, 2025. [v19.0 deprecation] The Airbyte Facebook Marketing connector has since been updated to address this: • It was updated to v21.0 via a fix for the v19.0 deprecation. [v19.0 fix] • It was subsequently updated to v23.0 (as v21.0 was set to be deprecated on September 9, 2025). [v23.0 migration] Action required: You should upgrade your

source-facebook-marketing

connector to the latest version (4.0.0+) to natively use v23.0 rather than relying on Meta's auto-upgrade. 2. Development Access Tier The header

x-fb-ads-insights-throttle

shows:

"ads_api_access_tier": "development_access"

This means your Facebook App is still on development access, not advanced access. This is likely the root cause of your rate limiting issues. Development access has much stricter throttling limits compared to advanced access. [App review guide] To fix this, you need to request Advanced Access for the

ads_management

and

ads_read

permissions through your Facebook App's App Review > Permissions and Features section. [App review guide] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.