@kapa.ai { "url": "https://airbyte-dev.t2q6.kitt-inf.net/workspaces/8c3ee3ce-4ab5-4efa-be18-0ec019fc9ee8/connections/a097bb2e-6c15-4b35-943a-98b5939d3feb/timeline", "airbyteVersion": "2.0.1", "errorType": "TypeError", "errorConstructor": "TypeError", "error": {}, "stacktrace": "TypeError: Cannot read properties of undefined (reading 'edition')\n at it (https://airbyte-dev.t2q6.kitt-inf.net/assets/App-i9ji1k08le.js:2:13336)\n at Ope (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:39:19643)\n at B8e (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:44390)\n at N8e (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:40078)\n at wht (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:40001)\n at GV (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:39849)\n at gre (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:36178)\n at R8e (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:41:35117)\n at k (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:26:1551)\n at MessagePort.O (https://airbyte-dev.t2q6.kitt-inf.net/assets/core-l0xde5f173.js:26:1916)", "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36", "featureFlags": {} }

You're encountering a UI crash with the error

TypeError: Cannot read properties of undefined (reading 'edition')

on the Connection Timeline page in Airbyte version 2.0.1. What's happening The error occurs in the frontend JavaScript when it tries to read an

edition

property from an object that is

undefined

. This is a UI-level crash, likely caused by the application receiving an unexpected or missing response from the backend API — specifically around instance/edition configuration. This is similar to a known pattern seen in other Airbyte UI issues where the frontend fails to handle an undefined or null API response gracefully. [UI Crash Issue] Possible causes and things to check 1. Backend API not responding correctly: The UI may be failing to fetch instance configuration (e.g.,

/api/v1/instance_configuration

), returning a 404 or empty response, leaving the

edition

field undefined. This was a known issue in earlier versions. [Helm Upgrade Issue] 2. Resource constraints: Check that your Airbyte deployment has sufficient memory and CPU. Resource exhaustion can cause backend services to return incomplete or malformed responses, which then crash the UI. 3. Misconfiguration: Ensure your deployment has the correct

edition

value set (e.g.,

community

,

pro

, or

enterprise

) in your configuration/values. Recommended steps • Check backend logs for errors around the time of the crash, particularly from the

airbyte-server

or

airbyte-api-server

pods/containers. • Verify the

/api/v1/instance_configuration

endpoint returns a valid response with an

edition

field. • Try a hard refresh (

Ctrl+Shift+R

/

Cmd+Shift+R

) or a different browser to rule out a stale cache issue. • Check resource usage on your deployment (memory, CPU, disk). • If you're on a Helm/Kubernetes deployment, confirm your

values.yaml

has

edition

properly set under

global

. The knowledge sources do not contain a specific fix documented for this exact error in version 2.0.1. If the issue persists after the above checks, I'd recommend opening a GitHub issue at airbytehq/airbyte with your deployment details and backend logs for further investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.