@kapa.ai - On our Airbyte instance we’re seeing the following error: Warning from source: Workload failed: workload-monitor-claim Airbyte could not start the process within time limit. The workload was never claimed We’re using Airbyte OSS on Azure kubernetes installed with helm. What is the problem here and how can we fix it ?

"Workload Was Never Claimed" Error This is a known issue in Airbyte 2.x (self-hosted on Kubernetes). The root cause is a dataplane group mismatch: the bootloader creates a new unnamed

dataplane_group

on install/upgrade, while workloads are routed to the original

AUTO

group. The workload-launcher registers under the new group and never sees the workloads assigned to the

AUTO

group, so they sit in

pending

forever. [GitHub Issue] Diagnosis Connect to your Airbyte database and run:

SELECT id, name FROM dataplane_group;

If you see two rows — one named

AUTO

and one unnamed — you have the mismatch. [GitHub Issue] Fix Options Option 1: Direct database update (most common fix) Move all dataplanes to the

AUTO

group:

UPDATE dataplane
SET dataplane_group_id = (
  SELECT id FROM dataplane_group WHERE name = 'AUTO' LIMIT 1
)
WHERE dataplane_group_id != (
  SELECT id FROM dataplane_group WHERE name = 'AUTO' LIMIT 1
);

Then restart the workload-launcher:

kubectl rollout restart deployment/airbyte-<release-name>-workload-launcher -n <your-namespace>

Confirm the fix by checking the launcher logs for:

INFO  Resuming ApiQueuePoller with <AUTO group UUID> and high
INFO  Resuming ApiQueuePoller with <AUTO group UUID> and default

[GitHub Issue] Option 2: API-based fix (no direct DB access needed) If you prefer not to touch the database directly, you can use the internal API from within the cluster:

# Get the correct group from the dataplanes API
CORRECT_GROUP=$(kubectl exec -n <NS> deploy/airbyte-server -- \
  curl -s http://localhost:8001/api/public/v1/dataplanes \
  | python3 -c "import sys,json; print(json.load(sys.stdin)[0]['regionId'])")

# Update the workspace to match
kubectl exec -n <NS> deploy/airbyte-server -- \
  curl -s -X POST http://localhost:8001/api/v1/workspaces/update \
  -H "Content-Type: application/json" \
  -d "{\"workspaceId\":\"<WORKSPACE_ID>\",\"dataplaneGroupId\":\"$CORRECT_GROUP\"}"

Then restart the workload-launcher as above. [GitHub Issue] ⚠️ Important Notes • This mismatch can be triggered by Helm upgrades or even config changes (e.g., enabling

auth: enabled: true

), not just version upgrades. • The fix may need to be reapplied after each Helm upgrade, as the bootloader recreates the mismatch on each run. • This is a confirmed bug being tracked internally by the Airbyte team. [GitHub Issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.