@kapa.ai instagram source user_insights error. 'GET' request to 'https://graph.facebook.com/v23.0/17841479123471737/insights?period=day&metric=follower_count%2Creach&since=2026-03-18T08%3A00%3A00%2B00%3A00&until=2026-03-19T06%3A06%3A09%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': 'A_3EHzwoMDVcgaMq4pYuQmS'}}'. Response (headers): '{'debug-link': 'https://www.meta.com/debug/?mid=36b97ebe5d36e838f4b89c763bf84bc8', 'error-mid': '36b97ebe5d36e838f4b89c763bf84bc8', 'Vary': 'Origin', 'x-fb-aed': '773', 'cross-origin-resource-policy': 'cross-origin', 'x-app-usage': '{"call_count":3,"total_cputime":0,"total_time":0}', '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': 'A_3EHzwoMDVcgaMq4pYuQmS', 'x-fb-trace-id': 'AswDzBRkII/', 'x-fb-rev': '1035370989', 'X-FB-Debug': 'oi1nKSE7zxJKTtovt0LGMmj0NX9lUCYrU4qH7SWiBjZ27vLRQMiSsSz8beky3czm7k9LieglIDHUTQyAQc0V2A==', 'Date': 'Wed, 18 Mar 2026 060612 GMT', 'Proxy-Status': 'http_request_error; e_fb_vipaddr="AcOpUR_WnAXzH-AuJkaD8gEnbr07xBkvu9CgSBTNmf48ujWHZ0yAy4ee8fzpUSBRTDdjF9ZtwxaxJ1h7_sTWQTlogbJEN29rbmSZ5Q"; e_clientaddr="AcPbrcTii2YtQXZCr1xN_i_hljq0kyyKuPP0ydXG7JQosHxGlY15lH2H3tWGaX1XVnhoS4D6mTt8Hc27brIWraTOx0Son2ATl0X9vCN3e7yp-5pGPw"; e_upip="AcP5BDHLx081_MDTHwc4Or_V_rZ62_IhI8zP14ifLXsXFizniarxf57SJT0sDPj8OPWo6O9XQfebQJX0P59e2S8MJv8M-a9qVamrZh34YxY"; e_fb_zone="AcPC0wG6C6wqBM6nu95IwnWLEPjwAC20Oum3ATmoN7ADORPvKzuKwT_5m7r-HLJO"; e_fb_twtaskhandle="AcM52TFQNUg7uka8SJJ9sAuAHPSah-ckhBcu7Jyi5O4rhNiWuTxOS8l4dNdnZLElw1DfVscScSwKrtLyOBjlakOCwEgYgUv0CraZYnqmgsyw_A"; e_proxy="AcPpwvcTMH861otXPDFqQrRW2-kVZROK4Sy8xz3GtTkF0geGbSPX2OXUBOjkZVFTMcuXaWDJt4y0hTwu7skU", http_request_error; e_fb_vipaddr="AcPmUhZY0aM2Dtgw_mjpyjasFeV2WP25-C_49ersO3h_SVNjj7INAjrcZDR6DtSgD_96bT0pYq0"; e_clientaddr="AcOHgS8DXYlIUDgAsK4cihGeDMfb3yEdgWB8CBX3khBkdd7uSHYwULQHJfvMX2yDATvMFFaGigJHEF-K8eE"; e_upip="AcNiIGYeX695vezDeY0Cc66FFUtF5VI1-CYR_Z-JmWumcD84GiQHgry1Abm-iDbi1QiV79PZURSRz2Kp3OcSL4dVCSmcEnNHbZS79g"; e_fb_zone="AcNWuhqnN4dFY8ZP0gsr6ZaJP0dvUCYVmctLvzzeJsvrcJ8V7CCyHJ6074eM-A"; e_fb_twtaskhandle="AcMR7NQZ5OAlkz1D6mtugYCRERCmB4q0PManI9H8hWF_DzPQcZZq6jn8UOwzJFprFFHRd2_7jN6rLh22TLJSmE_wBbZ9NpRHlf-TkHY"; e_proxy="AcMgK-0berwAXLStjTLiG4bsKM7xzAav8wgaPjfiXUhrxFvCL6HgiySVT5aWjansMrkorTCH2B3RSyLM"', 'X-FB-Connection-Quality': 'EXCELLENT; q=0.9, rtt=2, rtx=0, c=10, mss=1380, tbw=9367, tp=-1, tpl=-1, uplat=268, ullat=0', 'Alt-Svc': 'h3=":443"; ma=86400', 'Connection': 'keep-alive', 'Content-Length': '177'}'.

This is a known issue with the Instagram source connector's

user_insights

stream. The error occurs because the connector is sending a

since

parameter with a future or out-of-range date to the Meta API, which rejects it. Root Cause The problem is related to date/time handling in the

user_insights

stream. The connector computes `since`/`until` parameters using UTC, while the Meta API interprets day boundaries based on the account's local timezone. For accounts in timezones ahead of UTC (e.g., UTC+2), the UTC-derived timestamps can appear as future dates from Meta's perspective, causing the

(#100) since param is not valid

error. [GitHub Issue] In your case, the request was sent at

2026-03-18T06:06:12 GMT

but the

since

parameter was

2026-03-18T08:00:00+00:00

, which is effectively a future time relative to when the request was made — consistent with this timezone-related regression. Fix This issue was introduced as a regression in v4.2.18 and a fix was merged in v4.2.21 (released 2026-03-12), which adds a lookback window and filters future-dated records in

user_insights

to prevent the cursor from advancing past the current UTC time. [changelog] Recommended Actions 1. Upgrade to v4.2.21 or later — this version contains the fix for the future-date issue in

user_insights

. 2. If you cannot upgrade immediately, downgrading to v4.2.14 is a confirmed workaround — multiple users reported that rolling back to 4.2.14 immediately resolved the issue. [GitHub Issue] 3. As a temporary mitigation, you can also try setting your

start_date

to a recent value well within the 2-year window, though this may not fully resolve the intermittent failures. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.