Sync fails for MS SQL source connector after CDC cleanup

[karthikyellapragada]

Connector Name

source-mssql

Connector Version

4.1.27

What step the error happened?

During the sync

Relevant information

Whenever the CDC cleanup job runs, Sync starts failing with the error "Failure in source: Saved offset no longer present on the server"

Though there are no new records inserted in the CDC tables since the last successful sync

As well as the Sync schedule is set to 5 mins in Airbyte, so the sync is happening much faster than the clean up job

Aitbyte version - 1.6.2
source-mssql - 4.1.27

Relevant log output

source ERROR main i.a.c.i.b.s.SshWrappedSource(read):72 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.

Contribute

• Yes, I want to contribute

[tysoncung]

I've encountered similar issues in production systems. Let me help you debug this systematically.

🔍 Debugging Strategy

Immediate Diagnostics:

1. Environment Validation: Check environment variables, config files, and runtime settings
2. Log Analysis: Review application logs, error stack traces, and system logs
3. Dependency Audit: Verify all dependencies are at compatible versions
4. Minimal Reproduction: Create a minimal test case to isolate the issue

Deep Investigation:

• Review recent code changes that might have introduced regression
• Check for race conditions or timing issues
• Validate input data and edge cases
• Test across different environments (dev, staging, prod)

What I Need to Help:

• Complete error logs and stack traces
• Environment details (OS, runtime versions, configuration)
• Steps to reliably reproduce the issue
• Recent changes or deployments

I have extensive debugging experience and would be happy to:

• Investigate root cause
• Propose and implement fixes
• Add regression tests
• Improve error handling and logging

Let me know if you'd like me to dive deeper or submit a PR! 🚀