fix(source-mssql): Improve invalid CDC offset message

[devin-ai-integration]

What

Resolves https://github.com/airbytehq/airbyte-internal-issues/issues/16455
Related to https://github.com/airbytehq/oncall/issues/12670

Improve the source-mssql CDC warm-start error message for saved offsets that are no longer valid for SQL Server CDC logs. The previous message included the concrete saved LSN value and generic reset instructions, which made the user-facing message non-deterministic and harder to aggregate.

Requested by devin-ai-integration[bot] via the /ai-triage-error-message playbook.

How

• Replace the dynamic saved-LSN reason with a deterministic CDC retention-window reason.
• Update the fail-sync and reset-sync invalid CDC cursor messages to use SQL Server CDC terminology.
• Bump source-mssql from 4.4.7 to 4.4.8 and add a changelog entry linked to this PR.

Review guide

1. airbyte-integrations/connectors/source-mssql/src/main/kotlin/io/airbyte/integrations/source/mssql/MsSqlServerDebeziumOperations.kt
2. airbyte-integrations/connectors/source-mssql/metadata.yaml
3. docs/integrations/sources/mssql.md

User Impact

Users with invalid or aged-out SQL Server CDC offsets see a deterministic message that names the SQL Server CDC log range / retention-window cause instead of exposing an internal saved LSN value. Connector behavior and FailureType are unchanged.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

Testing

• /home/ubuntu/repos/airbyte/gradlew -p /home/ubuntu/repos/airbyte :airbyte-integrations:connectors:source-mssql:compileKotlin :airbyte-integrations:connectors:source-mssql:compileTestKotlin -x test
• pre-commit run --files airbyte-integrations/connectors/source-mssql/src/main/kotlin/io/airbyte/integrations/source/mssql/MsSqlServerDebeziumOperations.kt docs/integrations/sources/mssql.md airbyte-integrations/connectors/source-mssql/metadata.yaml (prettier and license passed; Spotless hook could not complete locally because Maven is not installed, so the ktfmt change was applied from CI output)

Important

Active progressive rollout warning for source-mssql.

• (Click to Approve:) Bypass the active progressive rollout warning for source-mssql in the PR comment here.

---

Devin session

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Detected source-mssql Active Rollout: true

Important

Active progressive rollout warning for source-mssql.

To bypass this warning, click on the matching checkbox in the PR description. Look for the checkbox text:

(Click to Approve:) Bypass the active progressive rollout warning for source-mssql in the PR comment

• Rollout version: 4.3.0-rc.10
• Rollout state: initialized

Version on master Branch: 4.4.7

• RC marker on master branch: false

PR Description Checkbox Status

• Bypass checkbox checked: true

ℹ️ More Information

Show/hide details...

🤔 What happens if this PR is merged

Checking the checkbox will allow the PR to merge, but it does not necessarily stop the active rollout by itself. The result of the PR merging depends on what connector version is published.

Expected outcomes by type of version number change:

If connector version is not modified in this PR...

No new connector version should be released, and the active rollout should continue unchanged.

If the connector version changes from RC to non-RC (GA) version...

The merged PR may publish the GA version and make it default for eligible non-pinned actors. The existing rollout is not stopped immediately by the merge, but the rollout worker can later cancel it as superseded when finalizing.

If the connector version increments to a higher `-rc` version...

The merged PR may publish a new release candidate and replace the active RC marker. The previous incomplete rollout is canceled without unpinning, and a new rollout is created for the subsequent RC version.

🔁 How to rerun this check

To rerun the check, simply check and uncheck the box, or else modify the PR description and/or title in any way.

Alternatively, you can find the Active Progressive Rollout CI workflow and manually rerun it (although this is generally slower than the above methods).

---

This comment will be updated as PR and/or rollout status changes.

Workflow run

[github-actions]

source-mssql Connector Test Results

 12 files   12 suites   45s ⏱️
116 tests 116 ✅ 0 💤 0 ❌
226 runs  226 ✅ 0 💤 0 ❌

Results for commit 794d782.

♻️ This comment has been updated with latest results.

[github-actions]

Deploy preview for airbyte-docs ready!

Project:	airbyte-docs
Status:	✅  Deploy successful!
Preview URL:	https://airbyte-docs-2p675944x-airbyte-growth.vercel.app
Latest Commit:	794d782

Deployed with vercel-action