@kapa.ai: ConnectorWatcher(handleException):200 - Error performing operation: io.airbyte.workers.workload.exception.DocStoreAccessException io.airbyte.workers.workload.exception.DocStoreAccessException: Unable to write output for 3754d047-af3e-4c46-ad14-a43141bd60b2_7d8808ea-0025-4e84-8c09-f4c34565a553_0_discove

This error means the connector-sidecar was able to run the connector, but failed when trying to write the connector’s output (for a

discover

operation) into Airbyte’s document store via the Workload API, resulting in a

DocStoreAccessException: Unable to write output for ..._discover

. From the knowledge sources, this pattern appears in multiple OSS/Kubernetes deployments and is linked to problems with the connector-sidecar talking to the Workload API server: - In several issues, the same

DocStoreAccessException: Unable to write output for ..._check

appears when the sidecar cannot reach or authenticate to the Workload API, or when the API returns 404/500 errors. [[helm SA issue](https://github.com/airbytehq/airbyte/issues/50979); [S3 DocStore error](https://github.com/airbytehq/airbyte/issues/59197)] - A related open issue describes that in OSS v2.0.1 the connector-sidecar does not receive the necessary auth tokens, so calls to

POST /api/v1/workload/{id}/output

fail with 404/500, causing exactly this

DocStoreAccessException

. [[Sidecar auth issue](https://github.com/airbytehq/airbyte/issues/70451); [HTTP 500 DocStore error](https://github.com/airbytehq/airbyte/issues/72826)] Because the sources don’t include a definitive, step‑by‑step fix, I can’t say exactly which of these applies to your setup, but based on them you should: 1. Check connector-sidecar logs for HTTP 404/500 errors around

WorkloadOutputApi.writeWorkloadOutput

or

WorkloadOutputWriter.writeOutputThroughServer

, which confirm it’s the same DocStore/Workload API issue. [[HTTP 500 DocStore error](https://github.com/airbytehq/airbyte/issues/72826)] 2. Confirm your Airbyte version and deployment method (OSS v2.x, Helm, etc.) and compare with the known OSS v2.0.1 sidecar auth problem. [[Sidecar auth issue](https://github.com/airbytehq/airbyte/issues/70451)] 3. If on Kubernetes/Helm, verify that workload pods have the correct service account and tokens configured, since missing service accounts have previously caused the same

DocStoreAccessException

. [[helm SA issue](https://github.com/airbytehq/airbyte/issues/50979)] If you can share your Airbyte version, deployment type (Docker vs Kubernetes/Helm), and a snippet of the connector-sidecar logs around this error, it would help map your case more precisely to one of the known issues above.