kapa.ai: 2026-03-13 134139,908 [main] ERROR i.a.c.ConnectorWatcher(handleException):200 - Error performing operation: io.airbyte.workers.workload.exception.DocStoreAccessException io.airbyte.workers.workload.exception.DocStoreAccessException: Unable to write output for b2e713cd-cc36-4c0a-b5bd-b47cb8a0561e_83d1a904-7515-417e-978a-577036977d0c_0_check at io.airbyte.workers.workload.WorkloadOutputWriter.writeOutputThroughServer(WorkloadOutputWriter.kt:86) at io.airbyte.workers.workload.WorkloadOutputWriter.write(WorkloadOutputWriter.kt:65) at io.airbyte.connectorSidecar.ConnectorWatcher.saveConnectorOutput(ConnectorWatcher.kt:187) at io.airbyte.connectorSidecar.ConnectorWatcher.run(ConnectorWatcher.kt:80) at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt:22) at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt) Caused by: java.io.IOException: HTTP error: 500 Internal Server Error

This error is a known issue in Airbyte OSS. The

DocStoreAccessException: Unable to write output

error occurs when the connector-sidecar fails to write its output to the Airbyte workload API server, resulting in an HTTP 500 Internal Server Error. [Github Issue] Root Cause The connector-sidecar container is unable to authenticate or communicate with the workload API server. This is a platform infrastructure issue — not a problem with the connector itself. It has been linked to a known issue where connector-sidecar containers do not receive the necessary authentication tokens to communicate with the workload API server. [Connector-Sidecar Auth Issue] Potential Workaround (Kubernetes/Helm deployments) If you are running Airbyte on Kubernetes with Helm, the following may help: • Set

API_AUTHORIZATION_ENABLED=true

in the ConfigMap • Ensure the

WORKLOAD_API_AUTH_HEADER

and

WORKLOAD_API_BEARER_TOKEN

environment variables are properly configured However, there is a known limitation where these tokens may not propagate to connector-sidecar containers. [Github Issue] Recommended Next Steps To help diagnose further, consider providing: 1. Airbyte version (e.g., v2.0.1, v1.x) 2. Deployment method (Docker Compose, Kubernetes/Helm, etc.) 3. Whether this is a new installation or a recent upgrade 4. Helm chart version (if using Kubernetes) This issue is actively tracked at airbytehq/airbyte#70451 and airbytehq/airbyte#72826. 👍 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 -v2.0.1 , Kubernetes

Based on your setup (Airbyte v2.0.1 on Kubernetes/Helm), this matches exactly the known bug described in the open GitHub issue. Here's what's happening and what you can try: What's Happening The connector-sidecar containers created by the workload-launcher are missing

WORKLOAD_API_AUTH_HEADER

and

WORKLOAD_API_BEARER_TOKEN

environment variables, causing 401/500 errors when trying to write results to the workload API server. [Connector-Sidecar Auth Issue] This has been confirmed as likely a bug or regression in v2.0.1 — not a configuration oversight. The workload-launcher has the tokens, but does not pass them to the connector-sidecar pods it creates. [Connector-Sidecar Auth Issue] What to Try Step 1: Ensure

API_AUTHORIZATION_ENABLED=true

is set in the ConfigMap

airbyte-airbyte-env

. (Without this, the output endpoint returns 404.) Step 2: Configure the auth tokens on all relevant components in your Helm values:

workloadApiServer:
  extraEnv:
    - name: WORKLOAD_API_AUTH_HEADER
      value: "Authorization"
    - name: WORKLOAD_API_BEARER_TOKEN
      value: "[your-token]"

worker:
  extraEnv:
    - name: WORKLOAD_API_AUTH_HEADER
      value: "Authorization"
    - name: WORKLOAD_API_BEARER_TOKEN
      value: "[your-token]"

workloadLauncher:
  extraEnv:
    - name: WORKLOAD_API_AUTH_HEADER
      value: "Authorization"
    - name: WORKLOAD_API_BEARER_TOKEN
      value: "[your-token]"

Known Limitation: Even after doing the above, the connector-sidecar pods may still not receive these variables. There is currently no documented Helm value to inject these into connector-sidecar containers, and no

sidecar.extraEnv

equivalent exists in the chart. [Connector-Sidecar Auth Issue] Recommendation This is an open bug. I'd recommend: • Watching/commenting on airbytehq/airbyte#70451 for updates or a fix. • Checking if a newer Helm chart version has addressed this propagation issue. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.