Hello my airbyte still not running any sync on 2.0...
# ask-community-for-troubleshootingb
Bohdan Tertyshnyi
10/22/2025, 1:50 PMHello my airbyte still not running any sync on 2.0 version. (original posted on releases date https://airbytehq.slack.com/archives/C021JANJ6TY/p1760524222333319)
Everything was working well before the update, but after upgrading to 2.0, the sync won't start.
The error I get is 'Airbyte could not start the process within time limit. The workload was never claimed.'
Airbyte runned without low-resource mode on GCP VM with 8 vCPUs, 16 GB Memory.
Any suggestions to fix it?
k
kapa.ai
10/22/2025, 1:51 PMNew message text here
b
Bohdan Tertyshnyi
10/22/2025, 2:13 PMScreenshot 2025-10-22 at 17.13.49.png
Bohdan Tertyshnyi
10/22/2025, 2:27 PM@Bryce Groff you asked about workload-launcher. Looks like it's running. But I don't know if it's running properly. Explain to me, please, how I can check it?
j
Januka Peiris
10/23/2025, 8:27 AMI've had the same issue...any luck?
c
Camille Lemaitre
10/23/2025, 4:31 PMhi! did you check this thread already?
No idea if the problem is the same on your end, but my problem was that no connector specific pods were really launched.
Basically on my install (abctl using a RDS external database), the jobs were being pushed to one dataplane_group but the workload launcher was listening to another one that was created after the 2.0.0 upgrade
I checked my Airbyte database (dataplane_group table and workspace).
👀 1
Camille Lemaitre
10/23/2025, 4:36 PMbefore that, I suggest you check the logs of the workload launcher, to understand if it attempts to launch connectors or not. In theory you can check it using kubectl logs
Copy code
docker exec -it airbyte-abctl-control-plane kubectl logs -n airbyte-abctl <name_of_the_workload_launcher_pod> --tail=300🙏 1