@kapa.ai I upgraded the airbyte version from 1.6.21 to 1.8.0 and I am having an issue seeing my connections in the UI, the sources and destinations are all there but the connection page is on the onboarding page asking me to create my first connection. The connection also exist in the DB server. how can I fix this UI issue?

You’re running into a known 1.8.x UI issue where existing connections don’t show up even though they’re present in the database. From the reports for 1.8.0–1.8.3: - Some users only see ~20 connections in the UI even though many more exist in the DB; the page looks like an “empty” onboarding screen. [[Helm 1.8.0 issue](https://github.com/airbytehq/airbyte/issues/65096); [Frontend connections issue](https://github.com/airbytehq/airbyte/issues/65131)] - Another user with 400+ connections saw the UI revert to the “no connections” onboarding screen because the backend query was slow enough to hit a load balancer timeout; increasing the ALB idle timeout fixed it. [[Frontend connections issue](https://github.com/airbytehq/airbyte/issues/65131)] Given what’s in the knowledge sources, the concrete actions you can try are: 1. Check for pagination / partial load Scroll to the bottom of the Connections page and wait a bit to see if more connections load. 1.8 introduced pagination and lazy loading on the Connections page, so only a subset may appear at first. [[Airbyte 1.8 release notes](https://docs.airbyte.com/release_notes/v-1.8#platform-changes)] 2. Check for timeouts in front of Airbyte If you’re behind a load balancer or reverse proxy (e.g., AWS ALB), increase the idle/HTTP timeout so the Connections query can complete. One user with many connections fixed the “looks empty” UI by raising the ALB idle timeout. [[Frontend connections issue](https://github.com/airbytehq/airbyte/issues/65131)] 3. Be aware this is a 1.8.0 bug Multiple users on 1.8.0 report that only a subset of connections (e.g., 20 of 100+) are visible even though all exist in the DB; this is tracked as an open issue and appears related to how the backend query and pagination are implemented. [[Helm 1.8.0 issue](https://github.com/airbytehq/airbyte/issues/65096); [Frontend connections issue](https://github.com/airbytehq/airbyte/issues/65131)] The knowledge sources do not provide a definitive, general-purpose fix beyond adjusting timeouts and waiting for a patched 1.8.x release. If increasing your load balancer/proxy timeout doesn’t help, the docs and issues don’t describe another reliable workaround besides staying on a pre‑1.8 version or waiting for a patched 1.8.x build that addresses the connections listing bug.

@kapa.ai was this patched in the future releases?

A message from kapa.ai