@kapa.ai 'GET' request to 'https://graph.facebook.com/v23.0/17841403294677793/insights?period=day&metric=follower_count%2Creach&since=2026-03-12T07%3A00%3A00%2B00%3A00&until=2026-03-13T05%3A37%3A25%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. Getting this error in the Instagram connection.

This error is a known Instagram source issue related to how the connector computes the `since`/`until` parameters versus how Meta validates the 2‑year window for insights data. [IG user_insights issue] Meta’s API only allows

user_insights

metrics for the last 2 years, and the connector currently builds `since`/`until` in UTC. For some accounts/timezones, this can intermittently push the effective

since

outside Meta’s allowed 2‑year window, which triggers: > (#100) since param is not valid. Metrics data is available for the last 2 years This is being tracked as an open bug for

source-instagram

v4.2.18. [IG user_insights issue] What you can do right now 1. Adjust the

start_date

in your Instagram source to a more recent date so that all computed

since

values are clearly within the last 2 years. This is a mitigation, not a guaranteed fix, but it has been suggested as the current workaround. [IG user_insights issue] 2. If the failures are tied specifically to

user_insights

/

user_lifetime_insights

, you can temporarily: ◦ Run a sync with those streams disabled to keep other streams flowing. 3. Monitor the GitHub issue for a permanent fix and version guidance: [IG user_insights issue] If you’re on Airbyte Cloud or have support, you can also open a ticket referencing that GitHub issue URL so the team can correlate your case with the ongoing fix. 👍 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 now the version is 4.2.20 for instagram but still facing the same issue

The knowledge sources only document behavior and bugs up to Instagram source v4.2.19 and specifically call out the

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

issue for *v4.2.18*; they do not mention a fix in 4.2.19 or 4.2.20, nor any change to the `since`/`until` logic for

user_insights

. [Instagram changelog; user_insights issue] So based on the available information: • This is still a known open issue with

user_insights

where the connector computes `since`/`until` in UTC, but Meta enforces the 2‑year window in the account’s local timezone, causing intermittent 400 errors. [user_insights issue] • There is no documented connector version yet (in the sources you provided) that definitively fixes this. Given that you’re on 4.2.20 and still seeing it, the recommended mitigations from the issue still apply: 1. Move

start_date

forward in the Instagram source config so that all computed

since

values are clearly within the last 2 years (with some buffer), even after accounting for your timezone offset. This may reduce but not always eliminate the error. [user_insights issue] 2. If the failures block your syncs, temporarily disable

user_insights

(and/or

user_lifetime_insights

) and run with the remaining streams until a fix is released. 3. Keep an eye on the GitHub issue for confirmation of a version that contains a proper fix, and consider commenting there with: ◦ Your connector version (4.2.20), ◦ Timezone of the Instagram account / server, ◦ Example failing `since`/`until` values from logs. [user_insights issue] If you’re using Airbyte Cloud or have support, open a ticket and reference that GitHub issue so the team can correlate your case with the ongoing investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.