Hello @kapa.ai I'l facing this transient error bug https://github.com/airbytehq/airbyte/pull/74803 some threads indicates that downgrading https://docs.airbyte.com/integrations/sources/mssql to 1.x version should resolve the issue. Which precise target version should I downgrade to, to bypass the issue ?

The knowledge sources provided don't contain specific information about the PR #74803 you're referencing, so I can't speak directly to that particular bug. However, based on the knowledge sources available, here are the version-pinning recommendations mentioned for related MSSQL source connector issues: • For the invalid timeout string regression (introduced in 4.3.x): users successfully pinned to

4.2.6

as a workaround. [source-mssql timeout issue] • For the CDC cold-start "redo log" error (versions 4.3.2–4.3.5): users also fell back to

4.2.6

for the initial full load. [CDC cold-start issue] • For the LSN validation regression on Azure SQL geo-replicas (v4.3.4): Airbyte support downgraded to

4.3.3

as a workaround. [LSN validation issue] Since you're asking about downgrading to a 1.x version specifically, the knowledge sources do not contain any recommendation to downgrade the

source-mssql

connector to a 1.x version for any of the known issues. The 1.x line is quite old (released around 2024) and lacks features like dedup support. My recommendation based on available evidence: If your issue is related to the 4.3.x regression family,

4.2.6

is the most commonly cited stable fallback. If it's specific to a 4.3.4+ regression,

4.3.3

may suffice. For a precise answer tied to PR #74803 specifically, I'd suggest checking the PR comments directly or opening a support ticket with Airbyte, as the knowledge sources here don't cover that specific pull request. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.