2026-04-11 201512 destination ERROR : Get file to upload: Accessing file: /tmp/21a00944-c4e9-486f-916f-378b8ae6986016295487462189507545.csv.gz 2026-04-11 201512 destination ERROR Apr 11, 2026 111512 PM net.snowflake.client.jdbc.cloud.storage.SnowflakeS3Client upload 2026-04-11 201512 destination ERROR : Starting upload from file /tmp/21a00944-c4e9-486f-916f-378b8ae6986016295487462189507545.csv.gz to S3 location: c3jb0000-s/stages/7879f89c-0604-464b-b66e-c3c55fce3967/2026/04/11/21/2DAF792A-3194-4C43-B853-E108ECCF4243/21a00944-c4e9-486f-916f-378b8ae6986016295487462189507545.csv.gz 2026-04-11 201515 destination ERROR Apr 11, 2026 111515 PM net.snowflake.client.jdbc.cloud.storage.SnowflakeS3Client upload 2026-04-11 201515 destination ERROR : Uploaded file /tmp/21a00944-c4e9-486f-916f-378b8ae6986016295487462189507545.csv.gz to S3 location: c3jb0000-s/stages/7879f89c-0604-464b-b66e-c3c55fce3967/2026/04/11/21/2DAF792A-3194-4C43-B853-E108ECCF4243/21a00944-c4e9-486f-916f-378b8ae6986016295487462189507545.csv.gz. It took 2,905 ms with 0 retries 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.jdbc.SnowflakeConnectionV1 close 2026-04-11 201540 destination ERROR : Closing connection with session id: 107911113314410 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.core.SFSession close 2026-04-11 201540 destination ERROR : Session 107911113314410 has been successfully closed in 38 ms 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.jdbc.SnowflakeConnectionV1 close 2026-04-11 201540 destination ERROR : Connection with session id: 107911113314410 closed successfully in 39 ms 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.jdbc.SnowflakeConnectionV1 initConnectionWithImpl 2026-04-11 201540 destination ERROR : Initializing new connection 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.core.SFSession open 2026-04-11 201540 destination ERROR : Opening session with server: https:/, account: rb92362, user: AIRBYTE, password is provided, role: airbyte, database: ANALYTICS_METRICSSERVER_EU, schema: IMPORT, warehouse: airbyte, validate default parameters: null, authenticator: null, ocsp mode: FAIL_OPEN, passcode in password: null, passcode is not provided, private key is not provided, disable socks proxy: null, application: airbyte_oss, app id: JDBC, app version: 3.20.0, login timeout: null, retry timeout: null, network timeout: 60, query timeout: null, connection timeout: null, socket timeout: null, tracing: null, private key file: null, private key pwd is not provided, enable_diagnostics: not provided, diagnostics_allowlist_path: null, session parameters: client store temporary credential: null, gzip disabled: null, browser response timeout: null 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.core.SFBaseSession logHttpClientInitInfo 2026-04-11 201540 destination ERROR : Driver OCSP mode: FAIL_OPEN, gzip disabled: false and no proxy 2026-04-11 201540 destination ERROR Apr 11, 2026 111540 PM net.snowflake.client.core.SFSession open 2026-04-11 201540 destination ERROR : Connecting to GLOBAL Snowflake domain

These log entries showing

destination ERROR

for file uploads, session opens/closes, and connection initializations are not actual errors — they are informational messages from the Snowflake JDBC driver that are being incorrectly logged at the ERROR level. This is a known issue with the

destination-snowflake

connector. After a version update, normal operational messages (such as file upload progress, session opening/closing) started appearing as

ERROR

log entries, even though the underlying operations completed successfully. [Wrong error logs issue] Looking at your logs specifically: • The file upload succeeded ("Uploaded file... It took 2,905 ms with 0 retries") • The session was closed successfully ("Session ... has been successfully closed in 38 ms") • A new connection is being initialized normally These are all successful operations. Other users confirmed the same behavior — Snowflake's Query Monitor showed no actual errors corresponding to these log entries. [Wrong error logs issue] What you should do: • Check whether your sync actually completed successfully in the Airbyte UI, rather than relying solely on these log messages. • If syncs are completing without data loss, these ERROR-level logs can be safely ignored for now. • If you are on an older version of the connector, consider checking if a newer version of

destination-snowflake

has addressed the log level issue. The knowledge sources do not confirm whether this specific log level bug has been fully resolved in a later connector version, as the GitHub issue was closed as stale without a confirmed fix. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.