I cannot see logs on timeline tab when I click on details the details are empty and my job is ongoing

This is a known issue that other users have encountered. Here are some things to consider: Possible Causes & Solutions 1. Post-upgrade issue (Helm/Kubernetes) If you recently upgraded to Airbyte version 2 (e.g., Helm chart 2.x), there is a known bug where no jobs start and logs show "No logs found for this job." This was reported as a duplicate of GitHub issue #68115. [GitHub issue] Following the instructions in that related issue resolved it for affected users. 2. Storage space issue (Kubernetes/MinIO) On Kubernetes deployments, missing logs can be caused by insufficient storage space for MinIO (the log storage path is

/storage

). Increasing the PVC size for MinIO has resolved this for some users. [K8s no logs] 3. Log server running out of space If you're running your own log server, it may be running out of disk space, which prevents logs from being written or retrieved. [Intermittent sync failures] General Troubleshooting Steps • Navigate to the connection's Job History tab and try selecting the three grey dots next to the sync, then choose View logs to open the in-app log viewer. [Browsing logs] • Try downloading the logs locally via the same menu — this may surface content not visible in the UI viewer. • If you're on a Kubernetes deployment, check the health and storage capacity of your MinIO or log storage pods. • If you recently upgraded to version 2, check GitHub issue #68115 for the specific fix that resolved this for other users. [GitHub issue] Could you share more details about your deployment type (Docker, Kubernetes, Helm) and Airbyte version? That would help narrow down the root cause further. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai: updating the dataplane_group_id

Based on the knowledge sources, here is how to update the

dataplane_group_id

to fix the issue where jobs don't start or logs are missing after an Airbyte upgrade. Root Cause After upgrading to Airbyte 2.x, the bootloader may create a new

dataplane_group

with a fresh UUID, while the workload-launcher registers under this new group but workloads are routed to the old

AUTO

group. This mismatch causes all syncs to be stuck. [Dataplane Group Mismatch] Diagnosis First, check if you have a mismatch:

SELECT * FROM public.dataplane_group;

If you see two rows (one named

AUTO

and one unnamed), you have the mismatch. You can also verify with:

SELECT w.id AS workspace_id,
       w.dataplane_group_id AS workspace_group,
       d.id AS dataplane_id,
       d.dataplane_group_id AS dataplane_group,
       d.enabled
FROM workspace w
JOIN dataplane d ON d.enabled = true
WHERE w.dataplane_group_id <> d.dataplane_group_id;

The result should be zero rows. If not, a correction is needed. [Connector-Sidecar Auth Issue] Fix Option 1: Direct Database Update Move all dataplanes to the existing

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-abctl-workload-launcher -n airbyte-abctl

[Dataplane Group Mismatch] Fix Option 2: Via Internal API (no direct DB access needed)

# 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. [Dataplane Group Mismatch] Fix Option 3: Helm Values (Preventive) To avoid this on future upgrades, add the following to your Helm values before upgrading:

global:
  dataplaneGroups:
    defaultDataplaneGroupName: "AUTO"

[airbyte services stuck] Verification After the fix, the workload-launcher logs should show:

INFO  Resuming ApiQueuePoller with <group-id> and high
INFO  Resuming ApiQueuePoller with <group-id> and default

> Note: The database fix may need to be reapplied after every

abctl local install

run, as the bootloader recreates the mismatch on each startup. [Dataplane Group Mismatch] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.