[bigpeopleareold]

Agreed. Teams on the web for my company continually has issues with random reloads. I traced it down thinking the problems has to do with an authentication server not sending CORS headers when requested, because each time the problem happened, there was a faulty request. I'd expect there is even some monitoring on it, but no, it continues to happen. The Windows application seems to get the most love anyway. I have to fumble around this, running for most stuff the Windows application in a Virtual desktop, but since the IT disallows sharing screens, have to switch to that terrible web version to share, hoping it will not crash in the middle of calls (which it would constantly do)

Also, the "new Teams" is missing functionality. It lost the auto-transcribe feature. Go figure.

Totally amateur hour work. I tried once to get my teammates to use Slack, but it's hard to adjust. Slack ain't perfect, but it just works in so many ways that Teams barely hangs on with.

[poundofshrimp]

I find it hard to believe CORS is the root cause. It’s more likely that the server returns an error response and _that_ response doesn’t include the CORS headers.

[bigpeopleareold]

You are probably right. However, if I remember correctly (it's been awhile), it was one of them that didn't return a CORS header, but a 200 status, but that led to a number of requests that failed. But regardless, as an SPA, the Teams application is not resilient to it.