Internal message: Failed to read the output of a successful workload 80a54ea2-9959-4040-aac1-eee42423ec9b_277613d2-0fac-4509-ba2c-77a3b747ce18_0_discover Failure origin: airbyte_platform Failure type: system_error @kapa.ai

The knowledge sources mention similar platform-level failures, but do not describe this exact error message or a definitive root cause/fix for it. I can only infer likely causes and next steps. Your error: •

Internal message: Failed to read the output of a successful workload ...

•

Failure origin: airbyte_platform

•

Failure type: system_error

is in the same family as other workload / output handling issues where the platform cannot read or persist connector output, even though the workload itself ran. In related issues, the problem is in the platform infrastructure / workload API / sidecar interaction, not in the connector configuration itself.[HTTP 500 issue] In a similar case, the platform reported a system error with

failureOrigin: airbyte_platform

and an internal message about not being able to track sync progress because the process exited without reporting status.[Sync progress error] Another issue shows the platform failing a workload after it cannot find or process the connector’s output files within a timeout, again marked as

airbyte_platform

/

system_error

.[Zendesk workload error] Given what’s available, recommended next steps are: 1. Check platform / workload logs ◦ Look at the logs for: ▪︎

workload-api

/

workload-launcher

▪︎ the

connectorSidecar

/

ConnectorWatcher

◦ In similar issues, stack traces around

WorkloadOutputWriter

and

WorkloadOutputApi.writeWorkloadOutput

showed HTTP 500s when writing or reading workload output.[HTTP 500 issue] 2. Verify infrastructure / storage for workload output ◦ Ensure the storage or volume used for workload output is reachable and correctly mounted for both the connector pod and the platform components. ◦ In related errors, the platform timed out or failed when trying to find or read connector output files, even though the workload pipeline itself reported completion.[Zendesk workload error] 3. Confirm no HTTP 5xx between sidecar and API ◦ If you see

HTTP error: 500 Internal Server Error

around

WorkloadOutputApi

or

WorkloadOutputWriter

, that indicates a platform-side bug or misconfiguration rather than a connector problem.[HTTP 500 issue] 4. Treat as platform/system issue, not connector config ◦ Since

failureOrigin

is

airbyte_platform

and

failureType

is

system_error

, focus on: ▪︎ Airbyte deployment configuration (Kubernetes / volumes / networking) ▪︎ Version-specific platform bugs (consider upgrading if you’re not on a recent version) Because the sources don’t document this exact message, if the problem persists you’ll likely need to open a GitHub issue with: • Full job logs (including workload / sidecar logs) • Your deployment details (K8s/AKS/other, Airbyte version, OSS vs Enterprise) • Whether other connectors and jobs succeed This will help the Airbyte team correlate your case with the existing workload-output issues referenced above. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.