I've started getting posthog connector error since last week or so:

Request to <https://app.posthog.com/api/projects/58544/events/?offset=470000&limit=10000&after=2026-02-25T18%3A00%3A32.113000%2B00%3A00&before=2026-02-25T19%3A41%3A37.000000%2B0000> failed with status code 400 and error message Offset is deprecated. Max supported offset value is 50000

I suppose the connector needs some updates but is there any solution to this somewhere yet?

You’re running into a known PostHog API change: the

/events/

endpoint now enforces a hard limit on

offset

(max 50,000), while the current Airbyte PostHog connector still uses offset-based pagination with large offsets (e.g. 470,000 in your error). [PostHog source; PostHog issue] From the open GitHub issue for this connector: • The

/api/projects/:project_id/events/

endpoint is deprecated. • Offset pagination fails for offsets > 100,000 (and in your case PostHog is now returning a 400 with “Offset is deprecated. Max supported offset value is 50000”). • The connector currently uses offset-based pagination with

limit=10000

, which breaks on larger datasets. [PostHog issue] PostHog’s own guidance (quoted in that issue) is to: 1. Switch to timestamp-based pagination instead of offset. 2. Increase

LIMIT

(they suggest up to 50,000). 3. Fix retry logic to resume from the last position instead of restarting from offset 0. [PostHog issue comment] However, according to the knowledge sources: • There is no released connector version yet that implements this new timestamp-based pagination or removes offset usage. • An internal tracking issue exists at Airbyte to handle this API deprecation, but no fix is documented as shipped. [Oncall tracking comment] So, based on the available information: • There is no documented, official workaround inside the existing PostHog source connector that will fully resolve this error today. • The problem is on the connector design (offset pagination against a now‑restricted/deprecated endpoint), not on your specific configuration. What you can do right now Given what’s in the docs and issues: 1. Upgrade to the latest

source-posthog

version if you haven’t already, in case incremental improvements have landed (but the sources do not confirm a fix for this specific offset deprecation yet). [PostHog changelog] 2. If you control PostHog and can reduce the data volume per sync window, you might temporarily: ◦ Narrow the time range (shorter sync windows) so that the connector doesn’t need to paginate as deeply, and offsets stay under PostHog’s limit. This is only a mitigation and may still fail as data grows. 3. Monitor the GitHub issue and internal tracking link for the upcoming connector update that will move away from offset-based pagination: [PostHog issue] Because the knowledge sources don’t show a completed fix or a configuration flag you can toggle to switch to timestamp-based pagination, I can’t point you to a definitive in-product solution yet. The safest path is to: • Treat this as a known connector limitation due to PostHog’s deprecation. • Track the linked GitHub issue for when the connector is updated to use timestamp-based pagination or a different API. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.