@kapa.ai - ERROR i.a.a.c.c.ClientConfigurationSupport(generateDefaultRetryPolicy$lambda$3):63 - Failed to call unknown. Last response: null java.io.IOException: HTTP error: 500 Internal Server Error

The error you're seeing:

ERROR i.a.a.c.c.ClientConfigurationSupport(generateDefaultRetryPolicy$lambda$3):63 - Failed to call unknown. Last response: null
java.io.IOException: HTTP error: 500 Internal Server Error

is a known issue in Airbyte where the connector sidecar fails to write its output back to the Workload API server, receiving an HTTP 500 response. [HTTP 500 issue] What's happening The connector sidecar (

ConnectorWatcher

) attempts to call

WorkloadOutputApi.writeWorkloadOutput

to report results. The call fails with a 500 Internal Server Error, and after exhausting all retry attempts (5 retries), it gives up: [HTTP 500 issue]

Retry attempt 1 of 5. Last response: null
Retry attempt 2 of 5. Last response: null
...
Retry attempt 5 of 5. Last response: null
ERROR - Retry attempts exceeded.
java.io.IOException: HTTP error: 500 Internal Server Error

The full stack trace points to: •

ConnectorWatcher.run

/

ConnectorWatcher.saveConnectorOutput

/

ConnectorWatcher.handleException

• →

WorkloadOutputWriter.write

• →

WorkloadOutputWriter.writeOutputThroughServer

• →

WorkloadOutputApi.writeWorkloadOutput

This is consistent with a connector sidecar authentication or connectivity issue with the Workload API server, as described in a related issue where the connector sidecar cannot authenticate to the Workload API Server. [Sidecar Auth Issue] Suggested steps 1. Check the Airbyte server/workload-api-server logs for more details on why it's returning 500 — the root cause is on the server side, not the sidecar. 2. Verify connectivity between the connector sidecar pod and the Workload API server (e.g., network policies, service DNS resolution). 3. Check authentication configuration — the sidecar may not be properly authenticated to call the Workload API. [Sidecar Auth Issue] 4. Ensure all Airbyte components are on compatible versions — mismatched versions between the server and sidecar can cause API incompatibilities. The knowledge sources do not contain a confirmed fix for this issue, as the GitHub issue (#72826) is still open. I'd recommend following that issue for updates or adding your details there. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.