@sohambasu963draftchecks…fix/metaads-get-insights-pagination → master1 files · +14 −0updated 9h agoCustomer report (High priority, waiting 24+ days): Plain thread https://app.plain.com/workspace/w_01JKXFGRQ1QC95DG0AH1NEKGKE/thread/th_01KS005KX3HA8KR591WC2YEND9/ — project Compass (pr_3e13BE77qrFH), log_sR95D6trg_zE, toolkit version 20260504_00.
METAADS_GET_INSIGHTS silently dropped limit and after: they were not in the request schema, so any values customers passed were discarded and never forwarded to the Graph API. Facebook then applies its default limit=25 with no cursor, making pagination impossible. Decimal (support bot) confirmed the diagnosis on May 19; the fix was never filed.
limit: Optional[int] and after: Optional[str] to GetInsightsRequest, matching the Pydantic style of neighboring fields. Note: after previously existed in this file only in the response-side PagingCursors model, never as a request field.params["limit"] when limit is not None, params["after"] when set), following the style of the neighboring conditionals.python3 -m py_compile apps/metaads/actions/get_insights.py passes.🤖 Generated with Claude Code