@kapa.ai I am using Airbyte 2.0.1 on-prem deployment. When I'm editing existing Builder's default concurrency, changing it from 1->4 and the max concurrency from NULL -> 8 it always reverts the default concurrency to 1 after publishing the builder Why? Is this a known issue?

Thinking completed I'm sorry, but the knowledge sources don't mention a known issue where Default Concurrency reverts to 1 after publishing in Airbyte 2.0.1, so I can't confirm whether this is a bug. What the documentation does say about these settings: • Default Concurrency can be an integer (for example

5

) or a string referencing a user config field (for example

"{{ config['concurrency'] }}"

). [Global Configuration] • Max Concurrency is a safety limit that applies when Default Concurrency is derived from user configuration. For example, if Default Concurrency is

"{{ config['max_workers'] }}"

and Max Concurrency is

10

, the connector never exceeds 10 concurrent requests. [Global Configuration] Max Concurrency is documented as relevant when Default Concurrency is a user-config reference. Pairing a fixed integer like 4 with a Max Concurrency of 8 is not described in the docs, so the UI may handle that combination differently. This is only a possibility, and the sources don't confirm it. Some things you could try: • Switch to YAML mode in the Builder and check whether

concurrency_level

(default and max) is saved as you set it. The Builder UI is a view over the YAML manifest. [Builder overview] • Try setting Default Concurrency as a user-config reference and see if it persists. • If it still reverts, check the Airbyte GitHub issues or open a new one with your version (2.0.1) and reproduction steps. The 2.0 release changed the Builder UI significantly, so a regression is plausible, but I can't verify that from the sources. [Airbyte 2.0 notes] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

I've tried using a user-config reference and it still does not persist. Anything else worth trying?

Thinking completed I'm sorry, but the knowledge sources don't describe this persistence problem or a fix for it, so I can't say why it happens. Here are some options based on what the sources do cover. 1. Edit the YAML directly and verify the saved result The Builder UI is a view over the YAML manifest, and you can switch between UI and YAML editing at any time. [Builder overview] Try setting

concurrency_level

in YAML mode, publish, then reopen the YAML to see whether the values were kept. The manifest format looks like this in other connectors:

concurrency_level:
  type: ConcurrencyLevel
  default_concurrency: "{{ config.get('num_workers', 25) }}"
  max_concurrency: 50

[Klaviyo manifest] If the YAML keeps the values but the UI shows 1, the problem is likely in the UI display. If the YAML itself reverts, it is likely happening on save or publish. 2. Make sure the connector version in use is the one you published Publishing a new version doesn't necessarily switch existing sources to it. If "Set as active version" is disabled in the Release modal, sources keep using their current version unless you change the active version in the Builder page table. [Forum: releasing versions] Also, existing sources of a custom connector need to be upgraded manually. [Forum: updating sources] Check that you are looking at the version you just published. 3. Use a Jinja default if you want a user-tunable value If you want users to control concurrency, the Airbyte docs show

"{{ config['num_workers'] or 10 }}"

as an example. When the default comes from config,

max_concurrency

is required as a safeguard. [ConcurrencyLevel reference] You would also need a matching

num_workers

field in your connector's user inputs (spec), as the Pipedrive connector does. [Pipedrive PR] 4. Report it If none of this works, I'd open a GitHub issue with your version (2.0.1), the steps you take, and the YAML before and after publishing. The knowledge sources don't confirm whether this is a known bug, so a report with that evidence would help the maintainers. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.