Daniel de Cloet
12/03/2025, 2:22 PM/api/public/v1/workspaces/<workspace ID>/definitions/sources/<source UUID>, the airbyte-server becomes unresponsive and is killed due to failing liveness checks.
Is this a known problem?kapa.ai
12/03/2025, 2:22 PM/definitions/* APIs: 1. In 1.6.0–1.6.1, updating custom Docker destination (and in some cases source) connectors via the UI/API could hang or fail; the server logs showed errors like Id not found: Could not find configuration for STANDARD_WORKSPACE: 00000000-0000-0000-0000-000000000000. A contributor confirmed there was “an issue” and that newer platform builds fixed custom source creation but still had a problem with version updates. [[1.6.1 custom update issue](https://github.com/airbytehq/airbyte/issues/59196)] 2. In 1.8.5, creating custom sources via the public /api/public/v1/workspaces/<WORKSPACE_ID>/definitions/sources endpoint caused the worker/connector pod to hang when writing the spec to the doc store, and the server side threw java.lang.IllegalStateException: Get Spec job failed. The legacy /api/v1/source_definitions/create_custom endpoint and the UI still worked. [[1.8.5 public API issue](https://github.com/airbytehq/airbyte/issues/68608)] In both cases: - The issue only appeared when using the public /definitions/* endpoints, not the legacy /api/v1/.../create_custom endpoints. - The symptoms included hanging requests and instability on the server side when the platform tried to run a spec job for the custom Docker image. [[1.8.5 public API issue](https://github.com/airbytehq/airbyte/issues/68608)] However, the available sources do not mention OSS 2.0.1 specifically, nor do they confirm whether this bug is still present or has been fixed in that exact version. So I cannot definitively say it is a documented, known problem for 2.0.1. What you can reasonably infer and try, based on prior reports: - There is historical precedent for bugs where custom connector creation/update via /api/public/v1/workspaces/.../definitions/... can cause jobs/spec resolution to hang and destabilize airbyte-server. [[1.6.1 custom update issue](https://github.com/airbytehq/airbyte/issues/59196); [1.8.5 public API issue](https://github.com/airbytehq/airbyte/issues/68608)] - As a workaround in earlier versions, users were able to: - Use the legacy /api/v1/source_definitions/create_custom endpoint (or the corresponding destination endpoint) instead of the public /definitions/* API, or - Perform connector updates via the UI, which uses a different code path. [[1.8.5 public API issue](https://github.com/airbytehq/airbyte/issues/68608); [Custom connectors docs](https://docs.airbyte.com/integrations/custom-connectors)] Given the lack of explicit 2.0.1 data in the sources, the best you can do is: - Treat this as likely related to the previously reported /definitions/* bugs. - Try updating the custom connector version via: - The UI (Workspace settings → Sources/Destinations → edit the connector and change the Docker image tag). [[Custom connectors docs](https://docs.airbyte.com/integrations/custom-connectors)] - Or, if still available in 2.0.1, the legacy /api/v1/source_definitions/... or /api/v1/destination_definitions/... custom endpoints, which worked for affected users in 1.8.5. [[1.8.5 public API issue](https://github.com/airbytehq/airbyte/issues/68608)] Since the knowledge sources don’t mention OSS 2.0.1 specifically, I can’t confirm this as an officially tracked “known issue” for that version. For a definitive answer, you would need to open a GitHub issue against the current OSS repo and reference the earlier related reports above so the maintainers can confirm whether 2.0.1 is affected as well.