Subject: Setting workspace-level concurrent sync limits in Airbyte Cloud Hi team! I’m looking for a way to limit the number of concurrent syncs at the workspace level in Airbyte Cloud to comply with our constraints (e.g., max 3 concurrent syncs). What I need: A way to ensure we never exceed X concurrent syncs (e.g., 3) across our entire workspace, regardless of how syncs are triggered (scheduled, manual, API, or Airflow). Questions: 1. Does Airbyte Cloud support setting a workspace-level concurrent sync limit? 2. If yes, where can I configure this (UI/API/CLI)? 3. If not available in UI, can this be configured on your backend for our workspace?

I’m sorry, but the knowledge sources do not mention any way to configure workspace-level concurrent sync limits in Airbyte Cloud. What we do have documented is: - For self-managed Enterprise, you can control concurrency via

MAX_SYNC_WORKERS

/

MAX_CHECK_WORKERS

(Helm values or worker env vars) and worker replicas, which effectively cap the number of concurrent syncs cluster-wide, not per workspace. [[Scaling Airbyte](https://docs.airbyte.com/platform/enterprise-setup/scaling-airbyte); [Worker config](https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#worker)] - The Airbyte Cloud limits docs only describe limits on workspaces, connectors, streams, fields, and record size; they do not mention any configurable concurrency or “max concurrent syncs” setting per workspace or per account. [[Cloud limits](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/understand-airbyte-cloud-limits)] Given that: 1. Does Airbyte Cloud support a workspace-level concurrent sync limit? The documentation does not state any feature for setting a workspace-level concurrent sync limit in Airbyte Cloud. I cannot confirm that such a setting exists. 2. Where to configure it (UI/API/CLI)? There is no mention in the docs of any UI, API, or CLI option in Cloud to set a “max concurrent syncs per workspace” value. 3. Can it be configured on the backend for a workspace? The knowledge sources do not mention any backend-only or support-configurable concurrency cap for individual Cloud workspaces. To pursue this further, you would need to contact Airbyte directly (e.g., via support or sales) and ask if there is an internal or plan-specific option that is not documented; that information is not present in the provided sources.