@kapa.ai: ERROR i.a.c.o.w.ReplicationWorker(safeClose):79 - Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource@4bc54046; recording failure but continuing. io.airbyte.workers.exception.WorkerException: Source has not terminated. This warning is normal if the job was cancelled.

The error you're seeing:

Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource@...; recording failure but continuing.
io.airbyte.workers.exception.WorkerException: Source has not terminated. This warning is normal if the job

yes

The error you're seeing:

WorkerException: Source has not terminated. This warning is normal if the job was cancelled.

is a known Airbyte behavior. Based on the knowledge sources, this message appears when the source process does not exit cleanly during or after a sync. Here's what's known about it: 1. It can be benign if the job was cancelled. The message itself says "This warning is normal if the job was cancelled." [source-snowflake issue] 2. It can occur even when data transferred successfully. There are reported cases where the sync status is marked as

FAILED

despite successful data transfer, with this error appearing during resource cleanup. [sync marked FAILED] 3. A known root cause is that

SourceReader

blocks inside `attemptRead()`/`isFinished()` (backed by

Iterator.hasNext()

), which can block on socket reads and is not interruptible. This means coroutine cancellation does not stop the reader when the destination fails and the queue is closed, leaving the source container running. [SourceReader hang issue] 4. It can also be triggered by an

OutOfMemoryError

in the source process, causing it to terminate abnormally. [OOM issue] To help diagnose your specific case, it would be useful to check: • Was the job manually cancelled or did it time out? • Are there any earlier errors in the logs (e.g., OOM, source connector errors)? • Did data actually get transferred to the destination? Could you share more of the surrounding logs to help narrow down the root cause? 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.