Rafael Felipe
02/21/2026, 10:57 PMkapa.ai
02/21/2026, 10:57 PMfailureOrigin: "destination"
• internalMessage: "Destination process exited with non-zero exit code X"
• externalMessage: "Something went wrong within the destination connector"
However, they do not explain the meaning of a specific non‑zero exit code (like 3) or give a generic root cause for this message. The actual cause is always inside the destination connector’s own logs, which are not included in the snippets. [replication-orchestrator]
From the available information I can only say:
• Airbyte is reporting that the destination connector container crashed or exited with error code 3 during the write phase of job 41 on attempt 4.
• To understand why, you must inspect the destination connector logs for that job/attempt; the platform log line you pasted is only a high‑level wrapper error. This same pattern appears across multiple issues and always requires looking at the connector’s own stacktrace or error message. [replication-orchestrator; S3 Data Lake]
The knowledge sources do not contain enough information to map exit code 3 to a specific problem or fix. You’ll need to:
1. Open the job details for jobId = 41 and attemptNumber = 4.
2. Check the destination logs (not just the replication‑orchestrator line) to find the underlying stacktrace or error message.
3. Use that specific error to troubleshoot or search in the Airbyte docs / issue tracker.
If you can share the destination connector type and its detailed logs for that job/attempt, I can try to match them against the existing issues more precisely. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.