@kapa.ai we are using the facebook marekting v5.0.0 connector to try and sync ad_creatives stream to bigquery. We are seeing it just sync the first page of results and not properly paginate through (the sync completes successfully with 25 or 100 records depending on page size we set). Have confirmed the ad account has many more creatives and the start date is way in the past. No other filters applied either at the source config level

I’m sorry, but the provided knowledge sources don’t contain connector‑specific details for the Facebook Marketing v5.0.0 OSS/source connector or known bugs about

ad_creatives

pagination. They only document: • The AI Agents Facebook Marketing connector’s

ad_creatives.list

and

ad_creatives.search

actions (which use cursor‑based pagination via

limit

and

after

). [Ad creatives list; Ad creatives search] • Generic pagination behavior and troubleshooting for connectors (page increment, offset increment, cursor‑based, and common issues like infinite pagination, missing records, and parameter injection problems). [Builder pagination; Pagination troubleshooting] Because of that, I can’t see: • How pagination is implemented in Facebook Marketing v5.0.0 specifically. • Any documented bug where

ad_creatives

stops after the first page. What you can do, based on the generic guidance: 1. Confirm the actual pagination method used by the connector (likely cursor‑based with

after

for the Marketing API, but this is not shown in the sources). 2. Check for “missing records” causes: ◦ Ensure pagination parameters are being injected correctly and match what the API expects. ◦ Verify that the page size you configured is within the API’s limits. ◦ Confirm that the pagination method (cursor vs page vs offset) matches the API’s behavior. [Pagination troubleshooting] 3. If you built or modified this connector using the Connector Builder, review: ◦ Pagination mode (Page Increment / Offset Increment / Cursor‑based). ◦ Stop condition (that it doesn’t evaluate to “stop” after the first page). ◦ Cursor extraction (that the “next page” token is actually read from the response). [Builder pagination; Pagination YAML] Given the lack of connector‑specific detail in the docs, the next concrete step is to: • Inspect the connector’s pagination configuration (if you have access to its YAML / Builder definition), or • Open an issue / ticket with Airbyte including: ◦ Connector: Facebook Marketing v5.0.0 ◦ Stream:

ad_creatives

◦ Page size used ◦ API response snippets showing a `next`/`after` cursor that isn’t being followed. That will let the Airbyte team confirm whether this is a configuration issue or a bug in that specific connector version. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.