Ishan Anilbhai Koradiya
11/23/2025, 5:50 AMkapa.ai
11/23/2025, 5:50 AM143 in Airbyte logs almost always means the process was terminated by Airbyte itself (SIGTERM), not that the connector crashed on its own. In other words, the job was cancelled or timed out, and then the worker reports: > Source/Destination process exit with code 143. This warning is normal if the job was cancelled. [[Running cancellation](https://discuss.airbyte.io/t/3171); [Sync cancelled large data](https://discuss.airbyte.io/t/2921)] Common underlying reasons, based on the docs and similar reports: 1. Heartbeat timeout / unresponsive connector Airbyte monitors “heartbeats” from source and destination containers; if one stops responding for too long, it assumes the job is stuck and cancels it. [[Heartbeats](https://docs.airbyte.com/platform/understanding-airbyte/heartbeats)] Causes of missed heartbeats include: - API sources that are slow, asynchronous, or heavily rate‑limited. - Database queries on large tables or with poor indexing (e.g., unindexed cursor column). - Destinations that are slow to write due to resource limits. 2. Job timeout / orchestration cancellation Temporal (the job orchestrator) may cancel a sync if it exceeds its configured timeout or if cancellation is triggered for some other reason, leading to the same 143 exit code and “Running sync worker cancellation…” log line. [[Running cancellation](https://discuss.airbyte.io/t/3171)] 3. Resource pressure, especially on large syncs Several users see 143 only when transferring larger volumes (hundreds of MB+), often with custom sources or heavier destinations; increasing pod/container memory is a common first recommendation. [[Custom source 143](https://discuss.airbyte.io/t/2291); [Gitlab 143](https://discuss.airbyte.io/t/589)] 4. Manual or external cancellation If a sync is manually cancelled in the UI or by external automation, you will see the same pattern and exit code. Because 143 just means “terminated”, you need to look earlier in the logs for the real cause: - Search for “heartbeat”, “Running sync worker cancellation…”, or explicit connector errors. - Check if the logs show a long period of no new records or progress before cancellation. - For Kubernetes/Docker, also check pod OOM/restarts from your cluster logs. If you share a larger slice of logs that includes the period before the Running sync worker cancellation / exit with code 143 lines, it should be possible to narrow down whether it’s heartbeat timeout, resource limits, or something connector‑specific.