Error when using custom low-code connector as a source

Summary

When creating a new custom low-code connector in version 0.57.3 and using it as a source, a ‘Discovering schema failed: Failed to run schema discovery.’ error occurs in the UI. The logs in Cloud Storage and GKE do not provide helpful information. The user is looking for a workaround for this issue. Additionally, there is a version mismatch error when using Builder.


Question

Whenever I create a new custom low-code connector in 0.57.3 and try to use it as a source, I get a “Discovering schema failed: Failed to run schema discovery.” error in the UI. The logs both in Cloud Storage and in GKE are no help. This is a Helm-deployed Kubernetes instance, for what it’s worth.

I’m seeing others in here and <#C01AHCD885S|ask-ai> having similar errors . . . has anyone found a workaround for this?

(I’m not sure if it’s related, but when I try to use Builder, I keep getting a Error handling request: The manifest version 0.83.0 is greater than the airbyte-cdk package version (0.79.1). Your manifest may contain features that are not in the current CDK version.—manually changing the version in YAML view works fine, but I’m not entirely clear why a brand new deployment would be out of sync with versions)



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["custom-low-code-connector", "source", "error", "schema-discovery", "version-mismatch", "builder", "workaround"]