sql server:

Exception occurred while getting the delegate read iterator, closing SSH tunnel io.airbyte.commons.exceptions.ConfigErrorException: Saved offset no longer present on the server. Please reset the connection, and then increase binlog retention and/or increase sync frequency

This error means the SQL Server CDC position (LSN offset) that Airbyte stored from the last successful sync is no longer available on the server because SQL Server’s CDC/transaction log cleanup has already removed it. As a result, the connector cannot continue incrementally from that point and fails with: >

ConfigErrorException: Saved offset no longer present on the server. Please reset the connection, and then increase binlog retention and/or increase sync frequency.

[Sync fails for MS SQL] How to resolve now 1. Reset the connection in Airbyte ◦ In the Airbyte UI, open this connection and perform a Reset. ◦ This will trigger a new full snapshot and re-establish a valid CDC starting point. 2. Prevent it from happening again You need to ensure the CDC/transaction log retains changes long enough for Airbyte to read them: ◦ Increase CDC / log retention on SQL Server Airbyte recommends at least ~7–10 days of CDC retention for MSSQL so that offsets don’t fall out of range between syncs. [MSSQL LSN retention] ◦ Or increase sync frequency Make sure your sync schedule is more frequent than the retention window, so Airbyte always reads changes before they are cleaned up. [CDC best practices] If, after increasing retention and/or sync frequency, you still see the same error immediately after a cleanup job, you may be hitting a connector bug similar to the open MSSQL issues; in that case, capturing full logs and referencing the existing issues when opening a ticket would be the next step. [Sync fails for MS SQL; MSSQL LSN regression] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.