This message was deleted.

This error matches a known open issue in the MSSQL source connector affecting versions 4.3.x when using CDC. [MSSQL redo-log issue] From the analysis in that issue: • Debezium reports

No previous offsets found

. • The connector starts with

snapshot.mode=recovery

, which expects existing redo log / schema history. • On a fresh or reset connection (no prior offsets / schema history), Debezium cannot find anything to recover and fails with: >

Could not find existing redo log information while attempting schema only recovery snapshot

[MSSQL redo-log issue] This is identified as a bug in the cold‑start path of the MSSQL source connector in 4.3.x; it is not caused by your SQL Server CDC configuration itself. [MSSQL redo-log issue] The destination error about missing terminal stream status (

Streams without a status message: [T_CHITS]

) is a consequence of the source failing mid‑sync. Current status • The issue is open and has been escalated to the internal engineering team for investigation. [MSSQL redo-log issue] • Comments indicate it still reproduces in 4.3.4 and 4.3.5. [MSSQL redo-log issue] Workaround (from the issue) Until a fix is released, the documented workaround is: 1. Use MSSQL source connector version 4.2.6. 2. Run an initial full load (non‑CDC) with 4.2.6 to establish offsets and schema history. 3. Then upgrade the connector to 4.3.x and switch to *incremental / CDC*; at that point, CDC runs successfully because the schema history exists. [MSSQL redo-log issue] The reporter notes this workaround can cause some data misses around the switchover, so you should plan the cutover carefully (e.g., during a low‑traffic window and/or with validation). Because you’re on Airbyte Cloud, you may need to: • Pin the MSSQL source to version 4.2.6 for the initial sync (if version pinning is available in your workspace), then • Upgrade to the latest 4.3.x after that initial load. If you don’t see 4.2.6 or can’t control the version in Cloud, you’ll need to contact Airbyte support referencing this GitHub issue so they can either pin the version for you or confirm when a fixed version is available. [MSSQL redo-log issue] At this time, the knowledge sources do not contain information about a released fix or configuration toggle that avoids this bug without the 4.2.6 → 4.3.x workaround. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

so, after the first import should i revert to the newest connector version?