Hi @alexbal, we are aware of this issue, and think that it is caused by a stale browser cache. Can you please try clearing the browser cache, relaunching the browser, and then going beack to the site?
@Elliot Kirk i reopend edge dev after seeing this ask, seems to be working ok now without the manual cache refresh (i assume it out flushed it at some point?)
