Konathala Chaitanya
12/03/2025, 10:46 AMSync failed
0 bytes
|
no records loaded
|
1h 40m 19s
Warning from replication: Airbyte could not start the sync process or track the progress of the sync.
See less
message='Airbyte could not track the sync progress. Sync process exited without reporting status.', type='io.airbyte.workers.exception.WorkloadMonitorException', nonRetryable=false
what is the errorkapa.ai
12/03/2025, 10:47 AMmessage='Airbyte could not track the sync progress. Sync process exited without reporting status.', type='io.airbyte.workers.exception.WorkloadMonitorException', nonRetryable=false From the linked issues, this message means: - Airbyte successfully claimed the work for your sync, but the sync process never started correctly or never reported its status back to the platform. [[MySQL issue](https://github.com/airbytehq/airbyte/issues/62485); [Helm workload-launcher issue](https://github.com/airbytehq/airbyte/issues/57011)] - As a result, the workload monitor can’t get heartbeats/progress from the worker and raises this warning: “could not start the sync process or track the progress of the sync”. [[Helm workload-launcher issue](https://github.com/airbytehq/airbyte/issues/57011); [All syncs hanging](https://github.com/airbytehq/airbyte/issues/55812)] In the UI this appears as: - 0 bytes / no records loaded / long duration, then a warning from replication with that message. [[Connection timeline](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-timeline#syncs-refreshes-and-clears)] The documentation and issues do not give a single root cause; depending on environment it has been associated with things like: - Storage / infrastructure problems (e.g., workload-launcher cannot talk to backing storage). [[Helm workload-launcher issue](https://github.com/airbytehq/airbyte/issues/57011)] - Connectors or platform jobs exiting unexpectedly before reporting status. [[All syncs hanging](https://github.com/airbytehq/airbyte/issues/55812); [Amazon SP error](https://github.com/airbytehq/airbyte/issues/53167); [GSC error](https://github.com/airbytehq/airbyte/issues/61498)] - Job processes that never actually start within the allowed time. [[MySQL issue](https://github.com/airbytehq/airbyte/issues/62485)] So, what is the error? It’s a monitoring/worker-level error saying: “The sync worker did not start or did not send progress/heartbeats, so Airbyte can’t track this sync, and it’s treated as failed.” The precise underlying cause (connector bug, infra/storage issue, resources, etc.) must be determined from your deployment and job logs; those causes are not specified in the docs beyond the examples above.