https://linen.dev logo
Join Slack
Powered by
```2026-02-16 01:24:08 destination ERROR DefaultDi...
# replication-ask-ai
q
Copy code
2026-02-16 01:24:08 destination ERROR DefaultDispatcher-worker-2 i.a.c.l.t.DestinationTaskLauncher$WrappedTask(execute):129 Caught exception in task io.airbyte.cdk.load.task.internal.InputConsumerTask@1a7c5a07 io.airbyte.cdk.TransientErrorException: 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: [routing_route]
	at io.airbyte.cdk.load.state.SyncManager.markInputConsumed(SyncManager.kt:116) ~[bulk-cdk-core-load-0.1.74.jar:?]
	at io.airbyte.cdk.load.state.PipelineEventBookkeepingRouter.close(PipelineEventBookkeepingRouter.kt:300) ~[bulk-cdk-core-load-0.1.74.jar:?]
	at io.airbyte.cdk.load.task.internal.InputConsumerTask.execute(InputConsumerTask.kt:117) ~[bulk-cdk-core-load-0.1.74.jar:?]
	at io.airbyte.cdk.load.task.internal.InputConsumerTask$execute$1.invokeSuspend(InputConsumerTask.kt) ~[bulk-cdk-core-load-0.1.74.jar:?]
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) [kotlin-stdlib-2.1.10.jar:2.1.10-release-473]
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704) [kotlinx-coroutines-core-jvm-1.10.2.jar:?]

Stack Trace: io.airbyte.cdk.TransientErrorException: 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: [routing_route]
	at io.airbyte.cdk.load.state.SyncManager.markInputConsumed(SyncManager.kt:116)
	at io.airbyte.cdk.load.state.PipelineEventBookkeepingRouter.close(PipelineEventBookkeepingRouter.kt:300)
	at io.airbyte.cdk.load.task.internal.InputConsumerTask.execute(InputConsumerTask.kt:117)
	at io.airbyte.cdk.load.task.internal.InputConsumerTask$execute$1.invokeSuspend(InputConsumerTask.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
k
This error is a known class of issues in Airbyte’s CDK v3 destinations: the destination finished reading all input, but at least one stream (
routing_route
in your case) never received a terminal 
STREAM_STATUS
message. From the knowledge sources: • The same error pattern appears across multiple connectors and destinations, always as `io.airbyte.cdk.TransientErrorException: Input was fully read, but some streams did not receive a terminal stream status message.`[ClickHouse issue; MSSQL CDC issue] • For declarative sources using 
source-declarative-manifest
with CDK v3 destinations (e.g., BigQuery 3.x), this has been confirmed as a source/platform bug: the source does not emit the required terminal 
STREAM_STATUS
messages, causing the destination to fail even though records are read successfully.[Streams status bug] • Similar stack traces and wording appear in other incidents (HubSpot, BigQuery, etc.), all pointing to missing terminal stream status messages rather than a configuration problem.[HubSpot auth issue; BigQuery temp tables] Based on these sources, this is almost certainly not caused by your 
routing_route
stream configuration itself, but by the source or platform not emitting the final 
STREAM_STATUS
for that stream. However, the knowledge sources do not provide: • A general, user-side fix for arbitrary connectors. • A configuration flag or YAML option you can set to force emission of 
STREAM_STATUS
messages (explicitly stated as not available for declarative manifests).[Streams status bug] Given those limits, the best you can do, based on the documented cases, is: 1. Identify your source and destination versions and compare them to the known problematic combinations (e.g., 
source-declarative-manifest
with CDK v3 destinations like 
destination-bigquery:3.x
).[Streams status bug] 2. If you are using a declarative manifest or a connector already mentioned in the issues above, treat this as a platform bug and: ◦ Open or update a GitHub issue with: ▪︎ Full stack trace (like you pasted), ▪︎ Source and destination connector names and versions, ▪︎ Which stream(s) are listed as missing status messages. ◦ Reference the existing issues so the team can link your case: ▪︎ Streams without status messages / declarative manifest + CDK v3[Streams status bug] ▪︎ Similar CDK v3 destination failures[MSSQL CDC issue; BigQuery temp tables] The knowledge sources do not describe a reliable workaround (such as a specific downgrade path or config change) that you can safely apply yourself; in some past incidents, fixes involved code changes or reverts on Airbyte’s side rather than user configuration.[Streams status bug] If you share your exact source and destination connector names/versions, I can help you map them more precisely to the known issues above, but any concrete fix will likely require an upstream change rather than a config tweak. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
q
airbyte/destination-bigquery: 3.0.16 airbyte/source-mongodb-v2: 2.0.7
13 Views
Open in Slack
PreviousNext
Powered by