Trouble with custom connectors connections

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Custom connectors connections failing with ‘Configuration check failed’ error in Airbyte Cloud


Question

Hello everyone !
I am having trouble with all my connections since this morning, involving both of my custom connectors. The connections all fail with the same error, and I get the same error when trying to modify the source and hit “Test and save”, or even the “Retest saved source”.
Everything worked correctly yesterday, I don’t know what happened ?
I am using Airbyte Cloud.
Here is the error :

Workload failed, source: unknown


Learn more
Internal message: Failed to find output files from connector within timeout of 9 minute(s). Is the connector still running?
Failure origin: airbyte_platform```
Thanks for your help !

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1732187102756209) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["custom-connectors", "connections", "error", "configuration-check-failed", "airbyte-cloud"]
</sub>
2

I don’t have a solution to this but I’m also getting the same error on my custom connectors. I think it’s an issue with the release of source-declarative-manifest:6.6.7, as my I’ve made no changes to my system and that’s the only thing that’s different since yesterday.

3

the same, don’t have a solution, but experiencing the same issue with our custom connector

4

I think the AIRBYTE_ENTRYPOINT environment variable is not set within the base source-declarative-manifest:6.6.7 image as the main container within the manifest-check pod gives the error: Entrypoint was not set! AIRBYTE_ENTRYPOINT must be set in the container. Hopefully there will be an update soon.

5

Created issue: https://github.com/airbytehq/airbyte/issues/48599

6

Same, my custom connectors are failing.

7

https://status.airbyte.com/cm3rfz0lu001lpu5ziy0p6848

8

A fix seems to have been implemented, custom connectors are working again