@kapa.ai "i18nParams": { "status": 500 }, "name": "HttpError", "requestId": "", "request": { "url": "/api/v1/web_backend/connections/list", "method": "post", "headers": { "Content-Type": "application/json" }, "data": { "workspaceId": "" } }, "status": 500, "response": { "message": "Internal Server Error: Invalid UUID string: ignore", "exceptionClassName": "java.lang.IllegalArgumentException", "exceptionStack": [], "rootCauseExceptionStack": [] } }

The error you're seeing:

"Internal Server Error: Invalid UUID string: ignore"

on the

/api/v1/web_backend/connections/list

endpoint is a known issue. Based on the knowledge sources, this type of 500 Internal Server Error can occur in self-hosted Airbyte deployments. The specific message "Invalid UUID string: ignore" suggests that a field expected to contain a valid UUID is instead receiving the string

"ignore"

— this is likely related to the

nonBreakingSchemaUpdatesBehavior

or a similar configuration field being set to

"ignore"

where a UUID is expected, or a misconfiguration in your connection/workspace settings. The knowledge sources do not contain a detailed root cause analysis or fix specifically for this

"Invalid UUID string: ignore"

error. However, based on a similar case documented in the Airbyte community [Forum Post], the recommended steps are: 1. Upgrade to the latest version of Airbyte, as many such internal server errors are resolved in newer releases. 2. Check your connection configurations for any fields that may have been set to

"ignore"

where a UUID value is expected. 3. Review your Docker logs for more detailed stack traces that could pinpoint the exact source of the issue. If the problem persists after upgrading, consider reporting it on the Airbyte GitHub Issues page with your full error details and Airbyte version. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I can't upgrade latest, I want 1.4.1 this version only, so how to fix this issue

The knowledge sources do not contain specific information about fixing the "Invalid UUID string: ignore" error on

/api/v1/web_backend/connections/list

for Airbyte version 1.4.1 specifically. Based on what the knowledge sources do cover, here are the general troubleshooting steps that have helped users with similar 500 errors on this endpoint: 1. Ensure a valid

workspaceId

is passed — your request shows an empty

workspaceId

(

""

), which is not a valid UUID. Make sure the correct workspace UUID is being sent in the request body. 2. Restart the Airbyte server — a contributor noted that a cache problem caused a similar 500 error, and restarting the

airbyte-server

container resolved it. [GitHub Issue] 3. Refresh the webapp — if you restarted Airbyte at any point, the webapp may be holding an outdated workspace UUID. Restarting or refreshing the webapp ensures it picks up the correct workspace UUID. [Forum Post] 4. Check server logs — review the

airbyte-server

container logs for a more detailed stack trace to identify the exact source of the

"Invalid UUID string: ignore"

message. Beyond these steps, the knowledge sources do not provide a version-specific fix for Airbyte 1.4.1. If the issue persists, I'd recommend reporting it on the Airbyte GitHub Issues page with your full error details and version number. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai: Internal message: Unable to persist the job Output, check the document store credentials. Failure origin: airbyte_platform

This error message: > "Unable to persist the job Output, check the document store credentials." > Failure origin:

airbyte_platform

is related to the connector-sidecar being unable to write output to the Airbyte Workload API server. This is a known issue in Airbyte OSS deployments. Based on the knowledge sources, the underlying cause is that the connector-sidecar fails to communicate with the workload API server, resulting in a

DocStoreAccessException

. The stack trace typically looks like:

DocStoreAccessException: Unable to write output for <workload-id>
  at io.airbyte.workers.workload.WorkloadOutputWriter.writeOutputThroughServer(WorkloadOutputWriter.kt:86)
  at io.airbyte.workers.workload.WorkloadOutputWriter.write(WorkloadOutputWriter.kt:65)
  at io.airbyte.connectorSidecar.ConnectorWatcher.saveConnectorOutput(ConnectorWatcher.kt:187)

This is linked to the connector-sidecar not receiving the necessary authentication tokens to communicate with the workload API server. [GitHub Issue] Potential workaround (for Kubernetes deployments): If you are using Kubernetes with Helm, some users have reported that ensuring the following environment variables are properly configured can help: •

API_AUTHORIZATION_ENABLED=true

in the ConfigMap •

WORKLOAD_API_AUTH_HEADER

and

WORKLOAD_API_BEARER_TOKEN

properly set However, there is a known limitation where these tokens may not propagate to connector-sidecar containers. [GitHub Issue] The knowledge sources do not provide a definitive fix specific to Airbyte version 1.4.1 for this error. I'd recommend checking the related GitHub issue [GitHub Issue] for further updates and workarounds from the community. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai: The authorization is disabled and so the connector API should not contact to workload API server

The knowledge sources do not explicitly address the scenario where authorization is disabled and whether the connector-sidecar should bypass the Workload API server authentication entirely. However, based on what is documented, one user reported a related finding: setting

API_AUTHORIZATION_ENABLED=true

in the ConfigMap

airbyte-airbyte-env

was required to make the

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

endpoint available (it was returning 404 before that). [GitHub Issue] This suggests that the

API_AUTHORIZATION_ENABLED

flag affects endpoint availability, not just authentication enforcement. So even with authorization disabled, the connector-sidecar still needs to communicate with the Workload API server to write job output — the two concerns (authorization and connectivity) appear to be separate. The knowledge sources do not contain enough detail to confirm whether disabling authorization fully resolves the

DocStoreAccessException

/ "Unable to persist the job Output" error in your specific setup. I'd recommend: 1. Verifying that

API_AUTHORIZATION_ENABLED

is correctly set in your ConfigMap. 2. Checking the connector-sidecar pod logs directly to confirm whether the error is still an auth-related 401/500, or a different connectivity issue. 3. Reviewing the open GitHub issue [GitHub Issue] for the latest community findings, as this is an ongoing known issue. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.