@kapa.ai I have the following error/warning

from destination: Input was fully read, but some streams did not receive a terminal stream status message. If the destination did not encounter other errors, this likely indicates an error in the source or platform. Streams without a status message: [advertisers, conversion_tracker, ppc_ad_images, ppc_ad_sets, publisher_event, ppc_ad_groups, ppc_ad_creatives, agencies, ppc_ads, ppc_ad_natives, ppc_accounts, ppc_campaigns, linear_workflows, ppc_ad_videos, user]

Source : airbyte/source-mongodb-v2: 0.1.13 Destination : BigQuery v3.0.19

This is a known bug affecting syncs where the source connector does not emit terminal stream status messages required by CDK v3 destinations like BigQuery 3.x. What's Happening When the destination (BigQuery v3.0.19, which uses CDK v3 / Bulk Load CDK) finishes reading all input, it checks that every stream received a terminal

COMPLETE

status message. If the source exits without emitting those messages — whether due to a crash, OOM, or a code-level limitation — the destination throws:

TransientErrorException: Input was fully read, but some streams did not receive a terminal stream status message.

The root cause can be on the source side (the source connector crashing or not emitting stream status messages) or the platform side (messages being dropped in transit). [Streams without status message] [Large stream sync failure] Your Specific Setup The knowledge sources do not contain specific information about

source-mongodb-v2:0.1.13

and this error. However, based on the pattern seen across multiple connectors (source-declarative-manifest, source-mssql, source-clickhouse, source-hubspot), the likely causes are: 1. The source connector is crashing (possibly OOM or an unhandled exception) before emitting terminal status messages for all streams. 2. The source connector does not implement terminal stream status message emission required by CDK v3 destinations. One contributor noted: "Looks like the source connector is crashing without logging anything. The destination correctly identifies that the source didn't finish cleanly. It's possible that the source pod ran out of memory." [Large stream sync failure] Recommended Actions 1. Check source logs carefully — look for errors, exceptions, or OOM signals in the source container logs, not just the destination error. 2. Downgrade the BigQuery destination to v2.x as a workaround — BigQuery 2.x uses the legacy CDK which does not require terminal stream status messages. Multiple users have confirmed this resolves the sync. [Streams without status message] 3. Report the issue on the Airbyte GitHub specifically for

source-mongodb-v2

if you confirm the source is not emitting status messages. > Note: As of the knowledge sources available (up to mid-2026), there is no official permanent fix for this class of issue across all affected connectors. Downgrading the destination remains the primary workaround while Airbyte works on a resolution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I downgraded the Bigquery Destination version to 2.10.2 as suggested but now I get the following error : “failureOrigin” : “replication”, “internalMessage” : “LEGACY states are deprecated.“, “externalMessage” : “Something went wrong during replication”, “metadata” : { “attemptNumber” : 0, “jobId” : 71 }, “stacktrace” : “java.lang.IllegalArgumentException: LEGACY states are deprecated.\n\tat io.airbyte.container.orchestrator.bookkeeping.ParallelStreamStatsTracker.getEmittedCountForCurrentState(ParallelStreamStatsTracker.kt:193)\n\tat io.airbyte.container.orchestrator.worker.state.StateEnricher.enrich(StateEnricher.kt:38)\n\tat io.airbyte.container.orchestrator.worker.ReplicationWorkerHelper.processMessageFromSource(ReplicationWorkerHelper.kt:324)\n\tat io.airbyte.container.orchestrator.worker.MessageProcessor.run(ReplicationTask.kt:158)\n\tat io.airbyte.container.orchestrator.worker.MessageProcessor$run$1.invokeSuspend(ReplicationTask.kt)\n\tat kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)\n\tat kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)\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\tSuppressed: io.airbyte.workers.internal.exception.DestinationException: No exit code found.\n\t\tat io.airbyte.container.orchestrator.worker.DestinationWriter.handleException(ReplicationTask.kt:129)\n\t\tat io.airbyte.container.orchestrator.worker.DestinationWriter.run(ReplicationTask.kt:108)\n\t\tat io.airbyte.container.orchestrator.worker.DestinationWriter$run$1.invokeSuspend(ReplicationTask.kt)\n\t\t... 5 more\n\tCaused by: java.lang.IllegalStateException: No exit code found.\n\t\tat io.airbyte.container.orchestrator.worker.io.ContainerIOHandle.getExitCode(ContainerIOHandle.kt:101)\n\t\tat io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource.getExitValue(LocalContainerAirbyteSource.kt:82)\n\t\tat io.airbyte.container.orchestrator.worker.DestinationWriter.run(ReplicationTask.kt:102)\n\t\t... 6 more\n”, “timestamp” : 1780588003167

I'm sorry, but the knowledge sources do not contain enough information to provide a confident answer about this specific error ("LEGACY states are deprecated") when using BigQuery destination v2.10.2 with source-mongodb-v2. What the Error Means Based on what is available in the knowledge sources, the Airbyte protocol defines three state types: STREAM, GLOBAL, and LEGACY. The

LEGACY

state type exists only for backwards compatibility and is explicitly noted as deprecated — "All current legacy cases are being ported to stream or global. Once they are, it will be removed." [State Types] This means your source connector (

source-mongodb-v2:0.1.13

) is emitting

LEGACY

state messages, which your current platform version no longer accepts. The Core Problem You are caught between two incompatibilities: • BigQuery v3.x → requires terminal stream status messages (which your source doesn't emit) • BigQuery v2.x → works with the destination, but your platform version now rejects

LEGACY

states emitted by the source Recommended Next Steps The knowledge sources do not contain a definitive resolution for this exact combination. I would suggest: 1. Upgrade

source-mongodb-v2

to a newer version that emits

STREAM

-type states instead of

LEGACY

states. 2. Open a GitHub issue at airbytehq/airbyte describing the incompatibility between

source-mongodb-v2:0.1.13

and your platform version. 3. Check your platform version — if it's recent enough to reject

LEGACY

states, a newer source connector version may resolve both issues simultaneously. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Can you suggest a source version that emits STREAM states but still works with MongoDB version 3.6 ?

The knowledge sources do not contain enough information to definitively recommend a specific

source-mongodb-v2

version that both emits

STREAM

states and is compatible with MongoDB server version 3.6. What the Knowledge Sources Do Tell Us • Version 1.0.0 (GA release, October 2023) introduced CDC-based incremental syncs and uses

GLOBAL

state (not

LEGACY

), since CDC connectors share state across streams. [MongoDB v2 docs] • Version 2.0.0 introduced multi-database support and is the most recent major version mentioned. [Migration Guide] • The MongoDB connector uses

GLOBAL

state type (not

STREAM

), because CDC via change streams requires shared state across streams — this is confirmed by the source code showing

AirbyteStateMessage.AirbyteStateType.GLOBAL

. [State Manager] • Version 1.0.0+ requires MongoDB replica sets and SSL/TLS. [Migration Guide] Important Caveat on MongoDB 3.6 The knowledge sources do not specify which MongoDB server versions are supported by each connector version. MongoDB Change Streams were introduced in MongoDB 3.6, but the connector documentation does not explicitly confirm compatibility with 3.6 for any specific connector version. Recommendation I'd suggest: 1. Checking the official MongoDB v2 connector changelog for version-specific compatibility notes. 2. Reaching out to Airbyte Support for a confirmed version recommendation given your MongoDB 3.6 constraint. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.