Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> 2026-02-13 16:25:51,257 [main]	*ERROR*	i.a.c.ConnectorWatcher(handleException):200 - Error performing operation: io.airbyte.workers.workload.exception.DocStoreAccessException

The log line you’re seeing:  ```text Error performing operation: io.airbyte.workers.workload.exception.DocStoreAccessException ```  indicates that the connector-sidecar failed to write its output (e.g., check connection or sync result) to the “doc store” via the Workload API. This same `DocStoreAccessException: Unable to write output for ..._check` pattern appears in multiple OSS issues and is generally a **platform / workload API** problem, not a connector-specific one.[[helm workload SA](<https://github.com/airbytehq/airbyte/issues/50979>); [S3 Minio](<https://github.com/airbytehq/airbyte/issues/59197>)]  From the issues, the most common root causes are:  1. **Workload API auth misconfiguration (Kubernetes / abctl / Helm)**      - 401/404/500 errors when the sidecar calls `POST /api/v1/workload/{id}/output`.[[workload 401 fix](<https://github.com/airbytehq/airbyte/issues/65567>); [sidecar auth bug](<https://github.com/airbytehq/airbyte/issues/70451>)]    - `WORKLOAD_API_AUTH_HEADER` / `WORKLOAD_API_BEARER_TOKEN` not aligned between:      - `airbyte-abctl-workload-api-server`      - `airbyte-abctl-worker`      - (and in some versions, not propagated to connector-sidecar).[[workload 401 fix](<https://github.com/airbytehq/airbyte/issues/65567>); [HTTP 500 docstore](<https://github.com/airbytehq/airbyte/issues/72826>)]  2. **Known OSS bug: connector-sidecar cannot authenticate to Workload API**      - Sidecar retries 5 times, all failing with HTTP 500/404, then throws `DocStoreAccessException`.[[sidecar auth bug](<https://github.com/airbytehq/airbyte/issues/70451>); [HTTP 500 docstore](<https://github.com/airbytehq/airbyte/issues/72826>)]  3. **General doc store / workload infra issues**      - Similar stack traces in other issues show the same exception when the doc store (backed by the workload API) is unreachable or misconfigured.[[helm workload SA](<https://github.com/airbytehq/airbyte/issues/50979>); [S3 Minio](<https://github.com/airbytehq/airbyte/issues/59197>)]  ### What you can try (Kubernetes / abctl / Helm)  Based on the reported workarounds:  1. **Align Workload API auth tokens** (if you’re on abctl / K8s):     ```bash    TOKEN=$(openssl rand -hex 24)     kubectl -n airbyte-abctl set env deployment/airbyte-abctl-workload-api-server \      WORKLOAD_API_AUTH_HEADER=Authorization \      WORKLOAD_API_BEARER_TOKEN=$TOKEN     kubectl -n airbyte-abctl set env deployment/airbyte-abctl-worker \      WORKLOAD_API_AUTH_HEADER=Authorization \      WORKLOAD_API_BEARER_TOKEN=$TOKEN    ```     Then restart the affected pods.[[workload 401 fix](<https://github.com/airbytehq/airbyte/issues/65567>)]  2. **If using Helm**, ensure:    - `API_AUTHORIZATION_ENABLED=true` in the ConfigMap.    - `WORKLOAD_API_AUTH_HEADER` and `WORKLOAD_API_BEARER_TOKEN` are set consistently for the workload API server and worker. Note there is a known limitation where these may not propagate to connector-sidecars in some versions.[[HTTP 500 docstore](<https://github.com/airbytehq/airbyte/issues/72826>); [sidecar auth bug](<https://github.com/airbytehq/airbyte/issues/70451>)]  Because the knowledge sources don’t include your exact deployment details or full logs, I can’t say precisely which of these is affecting you, only that your error matches these known workload API / doc store issues. If you share:  - Airbyte version, - Deployment method (Docker, K8s/Helm, abctl), - Whether this started after an upgrade,  I can map your situation more directly to the closest known issue and workaround.