@kapa.ai, every airbyte api is getting timeout issues, where the issue was not there before, was any change made to the airbyte version 2.0.1

Based on the knowledge sources, Airbyte version 2.0.1 has several known issues that could cause API timeouts and syncs getting stuck. Here's what's been reported: Known Issues in Airbyte 2.0.1 1. Dataplane Group Mismatch (Syncs Stuck in "Queued") A significant bug exists where the bootloader creates a new

dataplane_group

on every install/upgrade, while workloads continue to be routed to the old

AUTO

group. This causes all syncs to be stuck with the error: > "Airbyte could not start the process within time limit. The workload was never claimed." This affects both fresh installs and upgrades from 1.7.x. [Dataplane Group Issue] Workaround: Run the following SQL to move all dataplanes to the

AUTO

group, then restart the workload-launcher:

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
);

kubectl rollout restart deployment/airbyte-abctl-workload-launcher -n airbyte-abctl

> ⚠️ Note: This fix needs to be reapplied after every

abctl local install

run. 2. Connector-Sidecar Authentication Failure (504 Gateway Timeout) In Kubernetes/Helm deployments, connector-sidecar containers do not receive the

WORKLOAD_API_AUTH_HEADER

and

WORKLOAD_API_BEARER_TOKEN

environment variables, causing 401 Unauthorized errors and resulting in 504 Gateway Timeouts in the UI when testing connections. [Connector-Sidecar Auth Issue] 3. Get Stream Properties API Timing Out The

Get stream properties

API (

/api/public/v1/streams

) has been reported to run indefinitely after upgrading to newer versions, while other APIs like source/destination creation work fine. [Stream Properties API Issue] What changed in 2.0.1? The official release note for 2.0.1 only mentions an optimization to the heartbeat mechanism (fewer unnecessary database writes). [2.0.1 Release Notes] However, the issues above appear to be unintended side effects introduced in this version. If you're on Kubernetes/Helm, I'd recommend checking both the dataplane group mismatch and the connector-sidecar authentication issues as likely root causes for your API timeouts. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.