Getting this error and a “Application error: a client-side exception has occurred (see the browser console for more information).” error page when trying to edit the metrics for a live experiment where there is an archived metric in the metrics list. That is the only obvious difference when compared to other experiments where the metric edit screen works as expected. Deleting the metric resolved the error for us, but potentially an edge case other people will hit and they won’t want to delete the metric involved.

framework-45b23bd899ce37ec.js:1 TypeError: Cannot read properties of undefined (reading 'name')
    at [eid]-548e64021226b7c9.js:1:104923
    at Array.map (<anonymous>)
    at lt ([eid]-548e64021226b7c9.js:1:104846)
    at Eo (framework-45b23bd899ce37ec.js:1:63195)
    at xi (framework-45b23bd899ce37ec.js:1:120435)
    at bs (framework-45b23bd899ce37ec.js:1:109371)
    at gs (framework-45b23bd899ce37ec.js:1:109299)
    at vs (framework-45b23bd899ce37ec.js:1:109162)
    at as (framework-45b23bd899ce37ec.js:1:105942)
    at ls (framework-45b23bd899ce37ec.js:1:104493)
du @ framework-45b23bd899ce37ec.js:1
a.componentDidCatch.t.callback @ framework-45b23bd899ce37ec.js:1
Ua @ framework-45b23bd899ce37ec.js:1
ki @ framework-45b23bd899ce37ec.js:1
bi @ framework-45b23bd899ce37ec.js:1
yi @ framework-45b23bd899ce37ec.js:1
(anonymous) @ framework-45b23bd899ce37ec.js:1
ws @ framework-45b23bd899ce37ec.js:1
ls @ framework-45b23bd899ce37ec.js:1
S @ framework-45b23bd899ce37ec.js:1
T @ framework-45b23bd899ce37ec.js:1

main-99bf36b98c03ec19.js:1 TypeError: Cannot read properties of undefined (reading 'name')
    at [eid]-548e64021226b7c9.js:1:104923
    at Array.map (<anonymous>)
    at lt ([eid]-548e64021226b7c9.js:1:104846)
    at Eo (framework-45b23bd899ce37ec.js:1:63195)
    at xi (framework-45b23bd899ce37ec.js:1:120435)
    at bs (framework-45b23bd899ce37ec.js:1:109371)
    at gs (framework-45b23bd899ce37ec.js:1:109299)
    at vs (framework-45b23bd899ce37ec.js:1:109162)
    at as (framework-45b23bd899ce37ec.js:1:105942)
    at ls (framework-45b23bd899ce37ec.js:1:104493)
J

Hi Scott

yes we are, so you may have resolved this in a more recent code change

ya, we are checking internally