Im using mssql connector v5 and postgres connector v3 and airbyte version 2.0.0-alpha and airbyter helm chat version 1.9 .. while syncing from mssql to postgressql I am getting error of check the destination connection , but when I retest the destination connection its get connected without any error .. what could be the problem?

I'm sorry, but the knowledge sources don't contain enough specific information about your exact combination of MSSQL connector v5, Postgres destination connector v3, Airbyte 2.0.0-alpha, and Helm chart 1.9 to give a definitive answer. However, based on the available information, here are some likely causes and suggestions: Possible Causes 1. Intermittent Connectivity / Timing Issue The fact that the destination connection fails during sync but passes when manually retested is a classic sign of a transient/intermittent connectivity issue. The connection may be timing out or dropping under load. [MSSQL connector hang] 2. Known Bug in Postgres Destination v3.0.4 There is a known critical bug in Postgres Destination v3.0.4 where an invalid timestamp value

"{}"

is passed for the

_airbyte_extracted_at

column during COPY operations, causing all syncs and connection tests to fail:

ERROR: invalid input syntax for type timestamp with time zone: "{}"
Where: COPY _airbyte_connection_test_<guid>, line 1, column _airbyte_extracted_at: "{}"

This affects self-hosted Airbyte deployments. [Postgres Destination v3.0.4 bug] 3. Helm Chart Version Compatibility You are using Helm chart v1.9 with Airbyte 2.0.0. Note that version 2.0 is the final version supporting Helm chart V1, and there are known issues with the V1 chart for Airbyte 2.0. It is strongly recommended to migrate to Helm chart V2 to avoid instability. [Airbyte 2.0 release notes] Recommendations 1. Check your Postgres destination connector version — if it is v3.0.4, this is a known critical bug. Try pinning to an earlier version if possible. 2. Migrate to Helm chart V2 — Helm chart V1 is not officially supported beyond Airbyte 2.0, and there are known compatibility issues. [Helm chart V2 migration] 3. Re-validate connector settings — Go into the Connector Settings for both source and destination and re-test the connection to ensure no configuration drift occurred. [Postgres to Postgres failing] 4. Check Airbyte and worker logs for more detailed error messages during the failing sync, as the UI error may be masking the root cause. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.