2025-10-31 120931 replication-orchestrator ERROR Source process exited with non-zero exit code 1 2025-10-31 120931 replication-orchestrator ERROR SourceReader error: 2025-10-31 120931 replication-orchestrator INFO SourceReader finished. 2025-10-31 120931 replication-orchestrator INFO Source queue closed — stopping message processor... 2025-10-31 120931 replication-orchestrator INFO MessageProcessor finished. 2025-10-31 120931 replication-orchestrator INFO DestinationWriter finished. 2025-10-31 120931 destination INFO DefaultDispatcher-worker-1 i.a.c.l.t.i.ReservingDeserializingInputFlow(collect):55 Finished processing input 2025-10-31 120931 destination INFO DefaultDispatcher-worker-1 i.a.c.l.s.PipelineEventBookkeepingRouter(close):277 Maybe closing bookkeeping router 1 2025-10-31 120931 destination INFO DefaultDispatcher-worker-1 i.a.c.l.s.PipelineEventBookkeepingRouter(close):296 Closing internal control channels 2025-10-31 120931 destination INFO DefaultDispatcher-worker-1 i.a.c.l.m.MultiProducerChannel(close):26 Closing producer fileMessageQueue (active count=0, initialized count: 1) 2025-10-31 120931 destination INFO DefaultDispatcher-worker-1 i.a.c.l.m.MultiProducerChannel(close):30 Closing underlying queue 2025-10-31 120931 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.i.UpdateCheckpointsTask(execute):68 All checkpoints (state) updated 2025-10-31 120931 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartFormatter, part=0)) completed 2025-10-31 120931 destination INFO DefaultDispatcher-worker-5 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(io.airbyte.cdk.load.task.implementor.OpenStreamTask@436e287d) completed 2025-10-31 120931 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(io.airbyte.cdk.load.task.internal.UpdateCheckpointsTask@72b86258) completed 2025-10-31 120931 destination INFO DefaultDispatcher-worker-3 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartFormatter, part=1)) completed 2025-10-31 120931 destination ERROR DefaultDispatcher-worker-1 i.a.c.l.t.DestinationTaskLauncher$WrappedTask(execute):129 Caught exception in task io.airbyte.cdk.load.task.internal.InputConsumerTask@67035cbe 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: [sources, sample_data, company, api_keys, ingestion_logs, trino_ingestion_logs, source_logs, sync_logs, streams, login_attempts, users, objs, query_logs, refs] at io.airbyte.cdk.load.state.SyncManager.markInputConsumed(SyncManager.kt:116) ~[bulk-cdk-core-load-0.1.54.jar:?] at io.airbyte.cdk.load.state.PipelineEventBookkeepingRouter.close(PipelineEventBookkeepingRouter.kt:300) ~[bulk-cdk-core-load-0.1.54.jar:?] at io.airbyte.cdk.load.task.internal.InputConsumerTask.execute(InputConsumerTask.kt:117) ~[bulk-cdk-core-load-0.1.54.jar:?] at io.airbyte.cdk.load.task.DestinationTaskLauncher$WrappedTask.execute(DestinationTaskLauncher.kt:124) [bulk-cdk-core-load-0.1.54.jar:?] at io.airbyte.cdk.load.task.TaskScopeProvider$launch$job$1.invokeSuspend(TaskScopeProvider.kt:35) [bulk-cdk-core-load-0.1.54.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: [sources, sample_data, company, api_keys, ingestion_logs, trino_ingestion_logs, source_logs, sync_logs, streams, login_attempts, users, objs, query_logs, refs] 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.DestinationTaskLauncher$WrappedTask.execute(DestinationTaskLauncher.kt:124) at io.airbyte.cdk.load.task.TaskScopeProvider$launch$job$1.invokeSuspend(TaskScopeProvider.kt:35) 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) 2025-10-31

The error message you are seeing:

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: [sources, sample_data, company, api_keys, ingestion_logs, trino_ingestion_logs, source_logs, sync_logs, streams, login_attempts, users, objs, query_logs, refs]

indicates that Airbyte's destination component finished reading all input, but did not receive a "terminal stream status message" for some streams. This typically means that the source connector failed to properly complete the sync for those streams, possibly due to an error or crash in the source process. The log line:

Source process exited with non-zero exit code 1

confirms that the source connector process exited with an error, which is a common root cause for this type of issue. This pattern is seen in several Airbyte issues and discussions, where the destination reports missing terminal stream status messages when the source fails or crashes before completing all streams. The error is not specific to a single connector or destination, but rather is a general indication that the sync was interrupted or incomplete on the source side, and the destination could not finalize the state for the affected streams. This can be caused by: - Source connector bugs or unhandled exceptions - Resource exhaustion (e.g., out-of-memory, thread limits) - Platform or infrastructure issues - Misconfiguration or unsupported features in the source To resolve this, you should: 1. Review the source connector logs for more detailed error messages or stack traces that occurred before the process exited. 2. Check for known issues with the specific source connector you are using. 3. Ensure your environment has sufficient resources and is properly configured. 4. If the problem persists, consider opening a GitHub issue with detailed logs for further investigation. This behavior and error message are documented in several Airbyte issues, such as [source-hubspot mid-sync failures](https://github.com/airbytehq/airbyte/issues/62467), [MS SQL source connector after CDC cleanup](https://github.com/airbytehq/airbyte/issues/68150), and [source-clickhouse SQLFeatureNotSupportedException](https://github.com/airbytehq/airbyte/issues/61419), all of which describe similar symptoms and root causes.