@kapa.ai my instagram pipeline was working fine for the past week or so. getting this error after updation 'GET' request to 'https://graph.facebook.com/v23.0/17841479123471737/insights?period=day&metric=follower_count%2Creach&since=2026-02-28T08%3A00%3A00%2B00%3A00&until=2026-03-01T00%3A39%3A00%2B00%3A00' failed with status code '400' and error message: '(#100) since param is not valid. Metrics data is available for the last 2 years'. Request (body): 'None'. Response (body): '{'error': {'message': '(#100) since param is not valid. Metrics data is available for the last 2 years', 'type': 'OAuthException', 'code': 100, 'fbtrace_id': 'Ab6SYdERUeuh-qwpCWia6fd'}}'. Response (headers): '{'debug-link': 'https://www.meta.com/debug/?mid=36b97ebe5d36e838f4b89c763bf84bc8', 'error-mid': '36b97ebe5d36e838f4b89c763bf84bc8', 'Vary': 'Origin', 'x-fb-aed': '759', 'cross-origin-resource-policy': 'cross-origin', 'x-app-usage': '{"call_count":5,"total_cputime":0,"total_time":4}', 'Content-Type': 'application/json; charset=UTF-8', 'WWW-Authenticate': 'OAuth "Facebook Platform" "invalid_request" "(#100) since param is not valid. Metrics data is available for the last 2 years"', 'Access-Control-Allow-Origin': '*', 'facebook-api-version': 'v23.0', 'Strict-Transport-Security': 'max-age=15552000; preload', 'Pragma': 'no-cache', 'Cache-Control': 'no-store', 'Expires': 'Sat, 01 Jan 2000 000000 GMT', 'x-fb-request-id': 'Ab6SYdERUeuh-qwpCWia6fd', 'x-fb-trace-id': 'A2TjUKXPcao', 'x-fb-rev': '1034227922', 'X-FB-Debug': 'K0xOGY9ZOPaF1qsh7L8VgIYuYuSknGJUwMCLBf2U2Y/fr/7fSFJ3k5RIBcCFwhlL4IzSWaX+juNPOAO0lVn/VQ==', 'Date': 'Sat, 28 Feb 2026 003903 GMT', 'Proxy-Status': 'http_request_error; e_fb_vipaddr="AcOOqDhQAc5uuVmgt9zPQSPPqhYxpnUtPNlEJqJjcDEPtV3xAIOv4CUtTk2sDj9OLBjOM_sC6MTzgsHBRMpcMH3PJ7ivkBdX0kxi"; e_clientaddr="AcN-7pnw15OQI-je2G07dY5lhaXMr1fbdkhdLeVguqBKdiG4gtfu3hX8k8QBQ8Nn6vxk1wWWDd02lZWS7qNoF85QhN2dctt0ubU-P9yFIUlXbT8RVA"; e_upip="AcM4EIiTiM0bLdlugRJkvG5FLWFquvTyvFNEU9ihvydj0BsLnz80zFtC1-oQhEw5AROEAL73RRVbCd-iljOk3SS3N9czkACJmXk1ncUaVVM"; e_fb_zone="AcPY02kev6WN94f5TYDA0OnxgcWvQIxynk30lap1RbGpAmzQPQ-ofHuP2O8AS2hc"; e_fb_twtaskhandle="AcPR7YxYYxC0fCH3tSsoXgskQ-tJTCr_513yvttUgxaR2PBzKQAJwwS3EbCac-IRQHusxv8hBK2WAafDoW-cyN7w26hTqmZipCA-EsoPNe1VCSY"; e_proxy="AcPSQ2Agi82jxX6oR2mgdOVm2jNiXxh0ndtGlLmlvLaIZWsY3G4X1JSUE351_Mgk6JDcLFWEWP_c5hDU484", http_request_error; e_fb_vipaddr="AcMMqN6N_zjOpEdTPyE3M6LsHREQ-6Dx7yJOqtcnQ0-HBWbkqMerjXZUsO8SEoIzFfwwuw"; e_clientaddr="AcPByoDWhDdyH0Qw1JHfdN5HQHEx0PFMHFySzL_u9iW8p4lkSQ2le6iU9Dx8Vg6Lkd6gOCRnQ0hr9WCHKFc"; e_upip="AcMC5pxs3wN4aATfCmuj8uqepzFSU_BOXjwRYsu41dwCNKWPyUld_7wU-PCT9236B2fpm3atrZUbpCqEsIJxrZ9rULDlzMF_oKRc"; e_fb_zone="AcN3rbxB5T3gSIaajzR8oHV8TE4ml7MxSuRyBRtLPSFbS3lc-qQnTa60GVYOMw"; e_fb_twtaskhandle="AcPiJScr0klWrBCsX4HA5WANU_rL3NywT0roP4cPyae4_n7yVrUhmRy8oS-FzTWuuerk5UnSjDvxMbngGSlf4wWKZRLPxF0rwNzA"; e_proxy="AcNz3XzSrWbigZlBUkK8onyKgGG4DGjIGzSHjzB5fpd8eCFhm3fmGBnconB5bxtAQimFyfS8w9YKMvhh"', 'X-FB-Connection-Quality': 'EXCELLENT; q=0.9, rtt=24, rtx=0, c=10, mss=1380, tbw=3480, tp=-1, tpl=-1, uplat=118, ullat=0', 'Alt-Svc': 'h3=":443"; ma=86400', 'Connection': 'keep-alive', 'Content-Length': '177'}'.

This error matches a known issue in the Instagram source connector (v4.2.18) where the connector computes `since`/`until` in UTC, but Meta validates the 2‑year window using the Instagram account’s local timezone. That mismatch can intermittently push

since

just outside the allowed “last 2 years” window and trigger: >

(#100) since param is not valid. Metrics data is available for the last 2 years

This exact pattern (same endpoint, same metrics, same error) is described in the open GitHub issue for

source-instagram

v4.2.18. [IG issue 74059] Key points from that issue: • It appears after upgrading the Instagram connector to 4.2.18. • It affects the

user_insights

endpoint with

period=day

and metrics like

follower_count,reach

. • Root cause: *UTC-based date computation vs. account-local timezone*; Meta enforces “last 2 years” based on local midnight boundaries. [IG issue 74059] • It is currently tracked as an open bug; a similar pattern was already fixed for

source-facebook-marketing

. [IG issue 74059] What you can do right now (workaround) From the issue’s recommended mitigation: 1. Adjust your

start_date

forward so that the computed

since

is clearly inside the last 2 years from Meta’s perspective (e.g., move it a few days/weeks closer to “today” than strictly necessary). 2. Re‑run the sync. Because the problem is tied to timezone boundaries, this may reduce or eliminate the failures, but it is not guaranteed to fully fix them. [IG issue 74059] There is no documented permanent fix in a newer Instagram connector version yet in the provided sources; the issue is still open and tracked internally. [IG issue 74059] If the workaround is not sufficient, the issue suggests: • Monitoring the GitHub issue for updates: [IG issue 74059] • For additional help, using Airbyte Community Slack or, if you’re on Airbyte Cloud, opening a support ticket referencing that issue. [IG issue 74059] 👍 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 I am tired of adjusting the start date for more than 20 pipelines.

I’m sorry you’re running into this; based on the available information, there is no documented connector-side setting or fix yet that removes the need for per‑connection

start_date

adjustments. The GitHub issue only suggests adjusting

start_date

as a workaround and confirms this is a connector bug still being tracked. [IG issue 74059] Given the constraints of the knowledge sources: • There is no mention of: ◦ A patched Instagram connector version that fully fixes the `since`/timezone bug. ◦ A global configuration, environment variable, or UI option to bulk‑override

start_date

across many Instagram connections. • The only documented mitigation is to manually adjust

start_date

to keep

since

safely within the last 2 years, acknowledging that this is imperfect and can still be intermittent. [IG issue 74059] Because of that, the best next steps (from what’s documented) are: 1. Minimize changes: pick a conservative

start_date

(e.g., well within the last 2 years) for each Instagram source so you don’t have to keep moving it frequently. 2. Track the bug: subscribe to the GitHub issue so you’ll know when a proper fix or recommended version is available. [IG issue 74059] 3. If you’re on Airbyte Cloud, open a support ticket referencing that issue; if you’re self‑hosted, you can also raise your use case (20+ pipelines) in the issue comments or Community Slack to increase its priority. [IG issue 74059] I don’t have any documented way, from these sources, to avoid touching each pipeline individually. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.