Considering we have a POST option in connector builder, does it mean it can be used to build a destination connector?

👋 Hello, team!

Hi all, I am working a custom connector and as part of setting it up I got a local instance of Airbyte running. However, the http://localhost:8000/setup throws a React update depth error. Did anyone come across this before? And if so is there any way to get past it? This seems like a bug in Airbyte's UI but I haven't experienced it in production so it must be using a different version for the local instance.

Sorry, something went wrong.

Minified React error #185; visit <https://reactjs.org/docs/error-decoder.html?invariant=185> for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

I have opened an issue here too: https://github.com/airbytehq/airbyte/issues/76834

Turns out disabling basic auth fixed it.

It looks like the new bulk CDK currently only supports source / destination connectors using the Bulk CDK from the Java CDK. Are their plans to port the bulk CDK interface to Python so that, e.g. connectors using the concurrent CDK / Python CDK can also benefit from the speed improvements introduced?

DynamoDB Reserved Words Help

Hey friend octavia wave I have a question regarding an issue I am getting with DynamoDB. Basically I am trying to ingest data by using a connection on DynamoDB. However, our source is called

data

, which is a reserved word. When Airbyte tries to build the query (the

ProjectionExpression

), it sends the word

data

unquoted, and DynamoDB's API rejects it 😞 Even trying the Reserved attribute names doesn't work. We are using the free version. So I am wondering if some of you faced the same problem, or if you have any ideas for workarounds. Thank you so much for any tips keanu thanks

Hey team, I’ve raised a PR to add support for an optional

ig_account_id

filter in the Instagram source connector. Right now, we fetch all accounts tied to an access token, this change allows users to sync data for just one specific business account if needed. It’s fully backward compatible, so existing behavior remains unchanged. https://github.com/airbytehq/airbyte/pull/76916 Would appreciate a quick review when you get a chance. Thank you

Hi Team, we have been using Airbyte for months now and it helps us build report through Looker Studio. Unfortunately, it is stop syncing from Mar 10 until now, we have updated the Service Account Key JSON already but still it failed to sync. We are using Big Query as our database and pulls the data from Google Search console. Would appreciate any help from you. Thanks

Hello team, I have opened a PR to add a stream to your Chift connector - https://github.com/airbytehq/airbyte/pull/77576. Any idea on how I can convert it from draft to ready to review? Thanks

Hi team 👋 I have two open community PRs and would appreciate guidance on whether they're in scope for merge: 1. #74271 — source-productboard*: Adds

email

and

externalId

to the

users

stream schema. 3 files changed, schema-only, all CI green. Open since March 3. 2. #77530 — source-google-ads: Adds Service Account authentication alongside existing OAuth. Uses the existing SDK, includes migration + tests. Open since April 28. Both PRs have updated descriptions with review guides, examples, and testing instructions. I've tried to minimize review effort as much as possible. Questions: - Are these changes in scope for community contributions? - Is there anything missing that would help get them reviewed? Thanks for your time!

Our Airbyte Connectors to PostgreSQL occasionally throw "Saved offset is before replication slot's confirmed lsn" errors:

Saved offset is before replication slot's confirmed lsn. Please reset the connection, and then increase WAL retention and/or increase sync frequency to prevent this from happening in the future. See <https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting#under-cdc-incremental-mode-there-are-still-full-refresh-syncs> for more details.

We have tried both options for "Refresh your data" -- namely "Refresh streams and retain records" and "Refresh streams and remove records" -- as well as "Clear your data" and none of these address the issue. The only way we've found to fix this is to completely drop and recreate the Connection and/or the Source. This is fine when it's occasional, but we are now trying to stream data from PostgreSQL every two minutes (i.e., near real-time (NRT)). Last night, after running fine for hours, the Connector inexplicably started throwing the above error and has failed since. ---------------------------------- Here are the LSN lines from the last four successful syncs, with the last line being the first failed sync. I suspect that last "Saved offset LSN" shouldn't be the same value as the sync before it (i.e.,

19508285977976

).

2026-05-06 22:39:33 info INFO main i.a.i.s.p.c.PostgresDebeziumStateUtil(isSavedOffsetAfterReplicationSlotLSN):69 Replication slot confirmed_flush_lsn : 19508081354072 Saved offset LSN : 19508121385984

2026-05-06 22:43:34 info INFO main i.a.i.s.p.c.PostgresDebeziumStateUtil(isSavedOffsetAfterReplicationSlotLSN):69 Replication slot confirmed_flush_lsn : 19508124153352 Saved offset LSN : 19508167298192

2026-05-06 22:46:59 info INFO main i.a.i.s.p.c.PostgresDebeziumStateUtil(isSavedOffsetAfterReplicationSlotLSN):69 Replication slot confirmed_flush_lsn : 19508172623296 Saved offset LSN : 19508244459200

2026-05-06 22:48:34 info INFO main i.a.i.s.p.c.PostgresDebeziumStateUtil(isSavedOffsetAfterReplicationSlotLSN):69 Replication slot confirmed_flush_lsn : 19508244459200 Saved offset LSN : 19508285977976

2026-05-06 22:52:33 info INFO main i.a.i.s.p.c.PostgresDebeziumStateUtil(isSavedOffsetAfterReplicationSlotLSN):69 Replication slot confirmed_flush_lsn : 19508297437136 Saved offset LSN : 19508285977976

------------------------------------- Both myself and our Chief Architect have spent hours troubleshooting this issue and cannot find a solution. I suspect there is an issue in Airbyte's handling of LSNs. We need any ideas y'all have, please. If Airbyte is not reliable, using it for NRT is a non-starter.

Hi Airbyters! We are currently using

destination-clickhouse

in Airbyte for data loading, but at the moment, it appears to support only a single ClickHouse endpoint. Support for writing directly to a distributed ClickHouse cluster is becoming increasingly important for our use case, and I wanted to follow up on whether there is any expected timeline for this capability. I also noticed there is already a PR open related to distributed/replicated ClickHouse support: feat(destination-clickhouse): support Replicated database engine by KadekM · PR #76945 Given the growing need for production-grade ClickHouse deployments to operate in clustered/distributed modes, it would be very helpful to understand whether this feature is being prioritized and what the likely path forward looks like. If there is anything the community can do to help move this forward - testing, feedback, or validation - we would be happy to support. If there is already a recommended workaround or approach for loading into a distributed ClickHouse setup today, I’d also appreciate any guidance. Thanks!

@Mark Grivnin There is a PR for integrating the new stream https://github.com/airbytehq/airbyte/pull/77892 Are there any capabilities to review and merge it? Also looking forward to have it

Hey 👋 Nobody here on Airbyte Team to check this PR ? 🙏 Thanks 🙂

Dear Airbyte team, ⚠️ The current Facebook API version used in Airbyte connector will be deprecated

on June 9, 2026

. This issue has been opened to manage the upgrade. Please could you consider merge it ASAP ? Thank you 🙂

Hi team, Could you help bringing the current state of this ticket to production. I think that it is almost there. https://github.com/airbytehq/airbyte/issues/74764 Thank you so much! Update: @Rodi Reich Zilberman (Airbyte), @Simmon Li, Thank you guys for the responses in the ticket!

Hello Airbyte Team 👋 Are you considering enabling

speed mode

support for GCS destination connector like we implemented on the GCS Data Lake one ? The GCS destination is not maintained for a while and really suffers from scaling issues 😕 Thanks a lot for visibility !

⚠️ Critical Bug: Concurrent FlushWorker Race Condition Causing Silent Data Loss HI team 👋 We are hitting a severe concurrency bug in the Java CDK's async flush infrastructure (affecting Redshift/S3-staging destinations). Two

FlushWorker

threads occasionally pick up the same stream simultaneously, resulting in identical S3 keys where the second upload silently overwrites the first, dropping ~100k records per occurrence with zero error flags. There is an open issue and a proposed PR (

#76314

) tracking this—would really appreciate if this gets fixed soon 🙏

Hi Airbyte-Team, is someone able to Review https://github.com/airbytehq/airbyte/pull/77892 ? Thanks 🙂

Hi the Airbyte team 👋 I opened a PR fixing a long-standing source-gitlab bug: groups with >100 projects only sync the first 100, leaving merge_requests, commits, etc. incomplete. The root cause: project discovery reads the embedded projects array from GET

/groups/:id

(capped at 100) instead of the paginated GET

/groups/:id/projects

. Fixes #56916 (auto-closed by a bot, but still reproduces on master). PR: https://github.com/airbytehq/airbyte/pull/79707 Would appreciate a maintainer running

/run-connector-tests

and a review. Many thanks🙏

I've got an update to our connector waiting from Feb 😞 https://github.com/airbytehq/airbyte/pull/73740 .. is anyone available to look?

https://airbytehq.slack.com/archives/C054V9JFTC6/p1782147116962339 if anyone has a chance to look. mongo airbyte connection is essentially broken for a few of our connections and want to avoid forking the connector

Hi Airbyte Team ! I submitted two community connector PRs and all CI checks are passing. Could a maintainer take a look when they have time? It's my first time I upload connectors for my company, so please tell me if everything is ok ! github.com/airbytehq/airbyte/pull/79709 github.com/airbytehq/airbyte/pull/79710

Does the airbyte team have any SLA on reviewing code that is fully approved? Have a few PRs that are blocking some syncing on our side and would really like to get these merged.

It's an endless nightmare getting stuff merged @Henry Bogardus 😞 we have stuff open since Feb. It's been 12 months of battling to get stuff merged. It doesn't make sense to me as I feel like the whole power of an ETL product is the things it connects to, but we get no love.

hello all, i am currently working on the development of clickhouse connector to support multi-node, the only issue is that the custom connector is working only with stdio+ jsonl transport and not with socket + protobuf which causes the connector to insert slow. i have looked that the config is passed from the platform and stdio + jsonl are the default config in the env file. From testing perspective, can someone help me understand. is it because of the original definition id or there is a logic i am missing out on. it would be a great help , thanks.

Hi Airbyte Team 👋 I proposed this PR to make the

destination-gcs

connector much more fast thanks to sockets, aligned with destination-s3 connector 🏎️ Could you help me to review, validate and merge this PR ? 🙏 Thanks a lot !

Hi team! I'm looking for a time-sensitive review of a

source-salesforce

PR due to new security requirements: github.com/airbytehq/airbyte/pull/80892. The Salesforce connector breaks under Salesforce's OAuth Refresh Token Rotation mandate, and enforcement began June 25. Can a maintainer comment

/run-connector-tests

and queue this for review? Happy to turn feedback around same-day. Thanks!

Hello community, I reported an issue regarding the Connector Builder / Declarative CDK a while ago, and I would heavily appreciate it if someone from the team could take a look, as it severely impacts sync performance. When using

incremental_dependency: true

on parent-child streams, the child stream drops its cursor context after the first sync, forcing the parent stream into an unexpected full refresh loop on subsequent syncs (making them 100x–1000x slower). I just updated the issue with a comprehensive root-cause analysis (assisted by GitHub Copilot and verified against the latest Concurrent CDK source code). I also provided: 1. A functional connector-level workaround using custom components (StateMigration) that anyone can apply today. 2. The exact lines in the CDK core (

substream_partition_router.py

) where the context is being lost. Here is the link to the issue: github.com/airbytehq/airbyte/issues/61567 Could you please help review the proposed architectural fix or provide recommendations to get this merged? Thanks!