@kapa.ai Everything works with the source in the builder and the destination works in other connections. what could be the reasons of this issue? Sync summary: { “status” : “failed”, “recordsSynced” : 0, “bytesSynced” : 0, “startTime” : 1765803772778, “endTime” : 1765803788018, “totalStats” : { “additionalStats” : { }, “bytesCommitted” : 0, “bytesEmitted” : 0, “destinationStateMessagesEmitted” : 0, “destinationWriteEndTime” : 0, “destinationWriteStartTime” : 1765803776888, “meanSecondsBeforeSourceStateMessageEmitted” : 0, “maxSecondsBeforeSourceStateMessageEmitted” : 0, “meanSecondsBetweenStateMessageEmittedandCommitted” : 0, “recordsEmitted” : 0, “recordsCommitted” : 0, “recordsFilteredOut” : 0, “bytesFilteredOut” : 0, “replicationEndTime” : 1765803788012, “replicationStartTime” : 1765803772778, “sourceReadEndTime” : 1765803787989, “sourceReadStartTime” : 1765803776888, “sourceStateMessagesEmitted” : 0 }, “streamStats” : [ ], “performanceMetrics” : { }, “streamCount” : 2 } 2025-12-15 140308 replication-orchestrator INFO Failures: [ { “failureOrigin” : “destination”, “failureType” : “config_error”, “internalMessage” : “io.airbyte.cdk.ConfigErrorException: Failed to initialize connector operation”, “externalMessage” : “Failed to initialize connector operation”, “metadata” : { “attemptNumber” : 0, “jobId” : 61725921, “from_trace_message” : true, “connector_command” : “write” }, , “timestamp” : 1765803777482 }, { “failureOrigin” : “destination”, “internalMessage” : “Destination process exited with non-zero exit code 1”, “externalMessage” : “Something went wrong within the destination connector”, “metadata” : { “attemptNumber” : 0, “jobId” : 61725921, “connector_command” : “write” }, “stacktrace” : “io.airbyte.workers.internal.exception.DestinationException: Destination process exited with non-zero exit code 1\n\tat io.airbyte.container.orchestrator.worker.DestinationReader.run(ReplicationTask.kt:55)\n\tat io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invokeSuspend(ReplicationWorker.kt:152)\n\tat io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invoke(ReplicationWorker.kt)\n\tat io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invoke(ReplicationWorker.kt)\n\tat io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invokeSuspend(AsyncUtils.kt:22)\n\tat io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invoke(AsyncUtils.kt)\n\tat io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invoke(AsyncUtils.kt)\n\tat kotlinx.coroutines.intrinsics.UndispatchedKt.startUndspatched(Undispatched.kt:66)\n\tat kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:43)\n\tat kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:165)\n\tat kotlinx.coroutines.BuildersKt.withContext(Unknown Source)\n\tat io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1.invokeSuspend(AsyncUtils.kt:21)\n\tat kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)\n\tat kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)\n\tat io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:141)\n\tat io.micrometer.core.instrument.Timer.lambda$wrap$2(Timer.java:199)\n\tat datadog.trace.bootstrap.instrumentation.java.concurrent.Wrapper.run(Wrapper.java:47)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n\tat java.base/java.lang.Thread.run(Thread.java:1583)\n”, “timestamp” : 1765803788011 } ]

The log shows a destination-side configuration error:

text failureType: "config_error" internalMessage: "io.airbyte.cdk.ConfigErrorException: Failed to initialize connector operation" externalMessage: "Failed to initialize connector operation" ... Destination process exited with non-zero exit code 1

This pattern (destination exits with code 1, “Something went wrong within the destination connector”) appears in many issues where the root cause is inside the destination’s configuration or environment, not the source. [[BQ version mismatch](https://github.com/airbytehq/airbyte/issues/59702); [PG custom image](https://github.com/airbytehq/airbyte/issues/54691)] Based on the referenced cases, common reasons are: 1. Invalid or unsupported destination configuration for this specific connection - Wrong project/bucket/schema, special characters, or options that this destination version doesn’t accept. [[BQ project chars](https://github.com/airbytehq/airbyte/issues/48732)] - A subtle config difference from the “working” connections (e.g., dataset, namespace mode, table name, write mode). 2. Destination connector version vs platform mismatch - Some destinations require a minimum Airbyte platform version; otherwise they fail at startup with a config/initialization error. [[BQ version mismatch](https://github.com/airbytehq/airbyte/issues/59702)] 3. Destination image / registry issues - Using a custom image/registry (or a different tag) that doesn’t match Airbyte’s expected contract can cause the destination to fail immediately during initialization. [[PG custom image](https://github.com/airbytehq/airbyte/issues/54691)] 4. Destination-specific bug triggered only by this connection - In several issues the same destination worked for other connections but failed for a particular schema/operation (e.g., certain tables, deduping, or type casting). [[S3 dedupe failure](https://github.com/airbytehq/airbyte/issues/63359); [timestamp cast error](https://github.com/airbytehq/airbyte/issues/69032)] Because your failure is a generic

ConfigErrorException

without the connector’s inner error message, the knowledge sources don’t give enough detail to pinpoint the exact cause in your case. Next steps to diagnose: 1. Open the job logs and expand the **destination container logs**; look for: - A more specific error right before

Failed to initialize connector operation

(e.g., invalid field, missing permission, version message like “you must upgrade your platform”). [[BQ version mismatch](https://github.com/airbytehq/airbyte/issues/59702)] 2. Compare this connection’s destination settings with a working one: - Same connector version? - Same auth/project/bucket/DB? - Same namespace & normalization/deduping options? 3. If you’re using: - A custom destination image/registry: confirm it’s built from the correct Airbyte connector code and tag. [[PG custom image](https://github.com/airbytehq/airbyte/issues/54691)] - A recent destination version on an older platform: try downgrading the connector to an earlier version known to work on your Airbyte version, or upgrade the platform. [[BQ version mismatch](https://github.com/airbytehq/airbyte/issues/59702)] If you can share which destination you’re using and a snippet of the destination logs right before the config error, I can help narrow it down further.

The destination is Bigquery in airbyte cloud so it is running on the latest version. The test of the destination passes without issues. @kapa.ai

A message from kapa.ai

Turned out that changing 2 of the streams from full refresh deduped to to Full refresh overwrite solved the issue.