@kapa.ai - 2026-02-23 050134,461 [main] 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 at io.airbyte.api.client.interceptor.ThrowOn5xxInterceptor.intercept(ThrowOn5xxInterceptor.kt:16)

The knowledge sources show this exact stack trace appearing when the connector sidecar (or other Airbyte components) tries to call the Airbyte Workload API and receives an HTTP 500 from the platform, with the client then retrying and eventually giving up. [HTTP 500 forum; Workload 500 issue] However, they do not include a concrete root cause or fix; in similar cases the issue has been escalated for internal investigation and users are asked to provide more context (Airbyte version, deployment method, and full server/sidecar logs, including the failing HTTP request) so the team can debug. [HTTP 500 forum; HTTP 500 issue] Given that limitation, the only guidance I can confidently give from these sources is: 1. Capture the full error context: ◦ Open your browser dev tools → Network tab and inspect the failing request (status 500) and its response body. [HTTP 500 forum] ◦ Collect the corresponding server logs (Airbyte API / workload API) around the same timestamp, not just the sidecar log line. 2. Share that information: ◦ If you’re using the open-source edition, open or update a GitHub issue with: ▪︎ Airbyte version ▪︎ Deployment method (Docker, Kubernetes/Helm, etc.) ▪︎ Full stack trace and any server-side error message for the 500. [HTTP 500 issue] ◦ Or post it in the Airbyte Slack / forum thread so the team can correlate it with the known 500‑error investigations. [HTTP 500 forum] The knowledge sources do not provide a specific configuration change or patch you can apply directly; resolving this will require examining the full 500 response and server logs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.