@kapa.ai I couldn't do any changes on Airbyte UI ex: schema change or cron job. When I saved it, there was always error.

An unexpected error occurred. Please report this if the issue persists. (HTTP 500)

This generic “An unexpected error occurred … (HTTP 500)” message can be triggered by several different backend issues in Airbyte. From the material you provided, there are a few concrete patterns and mitigations you can check: 1. Enterprise sources cache issue (500 on

/list_enterprise_source_stubs

) If your UI/network logs show a failing request like: -

POST /api/v1/source_definitions/list_enterprise_source_stubs

with response

Internal Server Error: java.io.IOException: HTTP error fetching enterprise sources

, this is a known issue that affected both Airbyte OSS and Cloud. [[Enterprise sources 1](https://github.com/airbytehq/airbyte/issues/54058); [Enterprise sources 2](https://github.com/airbytehq/airbyte/issues/53609)] Temporary OSS workaround mentioned: - Host a file containing just

[]

(empty JSON array). - Set the

ENTERPRISE_SOURCE_STUBS_URL

environment variable to that file’s URL, then restart

airbyte-server

. [[Enterprise sources 1](https://github.com/airbytehq/airbyte/issues/54058); [Enterprise sources 2](https://github.com/airbytehq/airbyte/issues/53609)] The core issue was later fixed and cache cleaned on Airbyte’s side, so a restart/upgrade may also clear it. [[Enterprise sources 2](https://github.com/airbytehq/airbyte/issues/53609)] 2. Connector Builder / custom connectors after upgrade (1.7.x–1.8.x) If your HTTP 500 happens when: - creating or editing custom connectors, or - testing a declarative connector in the Connector Builder, then you may be hitting a known regression after upgrading to 1.7.1+ where the Builder reports invalid YAML and the backend

/connector_builder_projects/resolve

call returns 500. [[Builder 500](https://github.com/airbytehq/airbyte/issues/65568)] In Kubernetes installs, one user resolved it by correctly routing traffic for: -

/api/v1/connector_builder

→

airbyte-airbyte-connector-builder-server-svc

. [[Builder 500](https://github.com/airbytehq/airbyte/issues/65568)] 3. UI refresh / OAuth config issue in 1.8.x There is also an acknowledged bug where refreshing the UI or configuring OAuth could trigger HTTP 500 errors; Airbyte indicated a patch for 1.8.x would address those. [[Refresh UI](https://github.com/airbytehq/airbyte/issues/65070)] If you are on 1.8.x, upgrading to the latest 1.8 patch (or newer) is recommended. 4. How to identify the root cause Since many different backend failures surface as the same “unexpected error (500)” in the UI, you’ll need to inspect the failing API request: - Open your browser DevTools → Network tab. - Reproduce the error (e.g., save schema change / cron edit). - Look for any request returning 500 (e.g.

/discover_schema

,

/get

,

/connector_builder_projects/resolve

,

/source_definitions/list_enterprise_source_stubs

, etc.). This is the same approach support recommends when a schema refresh hangs or fails with 500. [[Mixpanel 500](https://discuss.airbyte.io/t/2814)] 5. When there isn’t enough info The knowledge you provided does not include a single universal fix for “can’t change schema or cron” in all versions; it mostly documents specific root causes (enterprise source cache, connector‑builder routing, UI refresh bug) plus the recommendation to check the exact failing endpoint and server logs. [[Enterprise sources 1](https://github.com/airbytehq/airbyte/issues/54058); [Mixpanel 500](https://discuss.airbyte.io/t/2814)] If you can share: - Your Airbyte version (e.g., 1.4.1, 1.7.1, 1.8.x, etc.), and - The exact API path that returns 500 from the Network tab, then it would be possible to map your case more precisely to one of the known issues above or conclude that it’s something new that should be reported.