This message was deleted.

Yes got the same on my lab NS which is on this version. Will check some customers and see

same on my lab as well on 33.52

Have several clients and even one of my my lab VPXs behaving the same. It's not 13.1 specific as I've seen it accessing 12.1 and 13.0 across multiple builds. I just revert to using aaad.debug from the CLI on those affected boxes. Some articles point to it maybe being browser based but have tested back old IE 11 and Chrome pre v90 and it still will not complete display. F12 does show some resources failing to load which is likely the cause.

37.38 does the samething, FYI

You definitely want to deploy the 54 build instead of the 52 as it was released to address the crashes in 52.

Cool thanks man