@kapa.ai: ERROR i.a.c.o.w.ReplicationWorker(safeClose):79 - Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@4355f900; recording failure but continuing. io.airbyte.workers.exception.WorkerException: Destination process exit with code 1. This warning is normal if the job was cancelled.

The error you're seeing:

Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@...; recording failure but continuing.
io.airbyte.workers.exception.WorkerException: Destination process exit with code 1. This warning is normal if the job was cancelled.

is a known pattern that appears across many different Airbyte connector combinations. Based on the knowledge sources, here's what's known: What This Error Means This error occurs during the replication process when the destination connector process exits with a non-zero exit code (1). The message "This warning is normal if the job was cancelled" is included by Airbyte itself, but it can also appear even when the job was not intentionally cancelled — indicating a real failure. [replication-orchestrator ERROR; S3 Data Lake failing] Common Causes This error has been reported in many contexts, including: • Destination connector bugs (e.g., BigQuery, MongoDB, MSSQL, Postgres, S3 Data Lake) [destination-bigquery special chars; destination-mongodb codec error] • Source connector failures that cascade into destination errors [source-shopify INCOMPLETE; source-zoho-crm] • Platform/infrastructure issues unrelated to the connectors themselves [sync hangs forever] • Version mismatches between the connector and the platform [destination-bigquery platform version] Recommended Steps 1. Check the full logs — look for earlier errors before this message, as the root cause is usually logged upstream (e.g., a specific exception in the destination or source connector). 2. Check for source errors — sometimes the source process fails first, which then causes the destination to exit with code 1. 3. Verify connector/platform version compatibility — ensure your connector version is compatible with your Airbyte platform version. [destination-bigquery platform version] 4. Check if the job was manually cancelled — if so, this error is expected and can be ignored. 5. Review the specific connector's known issues on the Airbyte GitHub for your source/destination combination. The knowledge sources do not provide a single definitive fix, as this error is a symptom that can stem from many different root causes depending on your specific connector setup. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.