@kapa.ai now theres a limit of 100 connections for self-hosted instances ? wtf ?

API error (HTTP 422): {"message":"Cannot create connection: organization has reached the maximum limit of 100 connections.organizationId=00000000-0000-0000-0000-000000000000
│ nConnections=100.","exceptionStack":[],"rootCauseExceptionStack":[],"errorId":"c952514b-34c1-49b0-92e1-c58beacc707d"}

Yes, this appears to be a real issue that others have encountered. A 100-connection limit is being enforced at the organization level even on self-hosted Airbyte instances, which is unexpected behavior for self-hosted deployments. [GitHub Issue] The Airbyte team has acknowledged the issue and escalated it internally, but as of now there is no documented workaround or configuration option to raise this limit. Specifically: • The 100-connection threshold appears to be enforced in the public connections API path, rather than via a documented environment variable or a setting in the default organization metadata. • It is not a known

abctl

environment variable like

MAX_CONNECTIONS_PER_ORGANIZATION

. • It is not documented as an intentional self-hosted limit. [GitHub Issue] What you can do right now 1. Comment on the GitHub issue to add visibility and share your Airbyte/abctl version: https://github.com/airbytehq/airbyte/issues/77876 2. Join the Airbyte Community Slack at slack.airbyte.com to check if others have found a workaround. 3. If you have an enterprise contract, open a support ticket at support.airbyte.com. I'm sorry I can't provide a direct fix — the knowledge sources do not contain enough information about a confirmed workaround or configuration parameter to override this limit at this time. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.