when I setup a new connection in airbyte, I specif...
# airbyte-agents-ask-ai
d
when I setup a new connection in airbyte, I specify all the streams I want, everything is set, but I get this message and I'm not allowed to continue. Unable to save the connection. Review the errors above to finish setup. There are no errors highlighted in the UI whatsoever.
k
This is a known issue that has been reported by other Airbyte users. Here are the most likely causes and fixes: "Unable to save the connection" with no visible errors 1. Browser Cache Issue (Most Common) This is the most frequently reported cause. Stale cached form data in the browser can cause the connection setup to fail silently. Fix: Clear your browser's application/cache data completely and try again. [GitHub Issue] 2. Missing Cursors or Primary Keys Even if nothing appears highlighted in red, some streams may have missing cursor fields or primary keys that are blocking the save. Fix: Go back to the Select Stream step and carefully check each stream for any missing cursor or primary key configuration. [GitHub Issue] 3. Xmin-based Streams Reporting "Missing Cursor" (Postgres-specific) If you're using the Postgres source connector version 3.8.x with the Xmin System Column cursor method, a regression causes streams to incorrectly report "Missing cursor" instead of
<source defined>
, blocking the save. [Postgres Regression] Fix: Downgrade the source-postgres connector to version 3.7.2 as a workaround. 4. Connection Limit Reached (Self-hosted) If you're on a self-hosted instance, there is a known bug where Airbyte enforces a 100-connection limit even on self-hosted deployments, blocking new connections entirely. [Connection Limit Bug] Fix: A patch was announced by the Airbyte CTO. Check if your instance is at or near 100 connections, and monitor the linked issue for the patch release. Recommended steps to try in order: 1. Clear your browser cache/application data fully and retry 2. Go back to the stream selection step and verify all cursors/primary keys are set 3. Check if you're near the 100-connection limit (self-hosted) 4. If using Postgres with Xmin, consider rolling back the connector version 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.