connection limit 100

100 Connection Limit in Self-Hosted Airbyte There is an open GitHub issue reporting that self-hosted Airbyte instances enforce a hard limit of 100 connections per organization, even for self-hosted deployments. [GitHub Issue] What's known • The error appears as an HTTP 422 with the message:Cannot create connection: organization has reached the maximum limit of 100 connections. organizationId=00000000-0000-0000-0000-000000000000 • This has been confirmed on at least Airbyte OSS v2.1.0 (Helm chart v2.1.0) and abctl deployments. [GitHub Issue] • The Airbyte team's initial investigation found that the 100-connection threshold is enforced in the public connections API path, rather than as a documented environment variable or a database metadata setting. [GitHub Issue] What's NOT yet documented The knowledge sources do not contain: • A specific environment variable (e.g.,

MAX_CONNECTIONS_PER_ORGANIZATION

) to override this limit • A database table/column to update for the default organization • Any official workaround or configuration guide The issue has been escalated to the Airbyte team for investigation, but as of the available information, no official fix or workaround has been published. [GitHub Issue] Recommended next steps 1. Follow the GitHub issue at https://github.com/airbytehq/airbyte/issues/77876 for updates. 2. Join the Airbyte Community Slack to ask for peer support or check for any community-discovered workarounds. 3. If you need urgent resolution, consider opening a support ticket if you have an enterprise agreement. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.