Right now it's just "Operation failed with unexpected error." and emails with invitations seem to be broken (either not sent or miss some important parts).
MS is so bad with error messages these days. "Oops something went wrong" and a "funny" picture of a dropped ice cream cone. Just tell me what is actually happening.
I find those cutesy error messages just make a bad situation worse.
Error descriptions are probably too much to ask these days - I would bet they'd be perceived as intimidating by the UX group, given that the same group seems to prefer a level of discourse appropriate for grade-school classrooms.
A error code would be wonderful, though, since it would be a nice unique search term. It could be put in small greyed-out text in a bottom corner, too, to make everyone happy.
One thing that keeps surprising me, even though it shouldn't by now, is how reluctant people are to learn from experience.
Rust's community got huge benefits out of work to improve the error messages from its compiler and tooling, but we didn't see a lot of real effort to mimic that even in other programming languages, let alone the wider tool ecosystem. A few people, here and there, put in some effort, but nothing at scale.
For Rust this work was imperative because their slogan is "A language empowering everyone to build reliable and efficient software" not "A language with terrible error messages that only nerds can handle" so I'm not surprised other people weren't doing this before Rust showed how much difference it makes, but I was surprised they didn't learn from that.
I wonder if - when the staffer wrote up a proposed mission and named it "Failed with unexpected error" as the placeholder codename - that would make politicians reconsider or they'd just rename it "Triumphant Awesomeness" or whatever instad of "Failed with unexpected error" and carry on anyway.
Lotus Notes all over again - worst piece of software on my computer.
It is something that was dragged out of a hackathon and succeeded thanks to Covid.
Well lotus notes would already completely crash if someone would send me the wrong animated gif on sametime. Dragging all my unfinished emails down with it too.
Teams is not quite as bad in terms of stability. The UX and performance are terrible though.
I have installed it while they still maintained an APT repository (which is now also empty). I have some older versions of the .deb files stashed away locally, from the time when teams still ran inside a docker container, but I would like to get a .deb file of the last released version. :-/
it seems that as long as you are logged in (in a desktop client / app on phone), it works. But as soon as you need to authenticate ( client / webbrowser / etc) , it fails.
It looks like the issue is region specific. While I was getting ""Operation failed with unexpected error" when trying to Join a meeting via invite, my counterparts in Europe were able to perform authentication and join meetings without any issues.
They are previewing a new version at the moment, it's quite a bit quicker and can switch between organisations very quickly too which was always a pain in the old version.
I didn't mean to make fun of you in any way! and am sorry if my comment came across that way. I often respond to title change requests with dumb title jokes as a way of making them less tedious.
HN is lucky to have so many non-native English speakers and they/you are all welcome here. We don't let HN users criticize others for their English - especially since most of the rest of us have no second language at all.
Share: Incident: TM612617, impacted service: Microsoft Teams, impacted feature: TeamsComponents, current status is: Service degradation
Published Time: 6/28/2023 7:50:04 AM
Current status: We’re reviewing a recent configuration change which may have unexpectedly resulted in impact. We’re determining our next steps to resolve the impact.
This quick update is designed to give the latest information on this issue.
Published Time: 6/28/2023 7:17:19 AM
Title: Users may be unable to access the Microsoft Teams service
User impact: Users may be unable to access the Microsoft Teams service.
More info: Users may be unable to load Microsoft Teams via the "teams.microsoft.com" web page and desktop app.
Users may see an “Operation failed with unexpected error” message.
While we're focused on remediation, users with access to a desktop build that is cached, may not experience the impact.
Current status: We’re reviewing application logs to identify the root cause and determine a mitigation plan.
Scope of impact: Impact is specific to users who are served through the affected infrastructure and are not using a cached desktop build.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
Published Time: 6/28/2023 6:43:01 AM
Title: Users may be unable to access Microsoft Teams using web browsers
User impact: Users may be unable to access Microsoft Teams using web browsers.
More info: Specifically, users may be unable to load the "teams.microsoft.com" web page and see the error message "Operation failed with unexpected error."
Current status: We're reviewing service monitoring telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to any user who is served through the affected infrastructure.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
I wish my company had an official unofficial chat app other than Teams. Many people will find what other apps people are already on, and then use those apps to avoid using Teams. Some are on Slack, others Discord, some Signal, and we have various other chats going on in those apps because attachments, code snippets, and other functionality is so inconvenient on Teams.
Anything official that needs to be shared and recorded for the company or requires widespread notification is through Teams, but then individuals are all using their own apps and management thinks Teams satisfaction is above 90% according to some surveys that no one I've talked to has filled out.
OT: Firefox just asked me if login.microsoftonline.com should be allowed to use it's cookies on teams.microsoft.com. I've never seen a prompt like that before. I like it. Is it a new feature?
46 comments
[ 3.3 ms ] story [ 117 ms ] threadError descriptions are probably too much to ask these days - I would bet they'd be perceived as intimidating by the UX group, given that the same group seems to prefer a level of discourse appropriate for grade-school classrooms.
A error code would be wonderful, though, since it would be a nice unique search term. It could be put in small greyed-out text in a bottom corner, too, to make everyone happy.
Rust's community got huge benefits out of work to improve the error messages from its compiler and tooling, but we didn't see a lot of real effort to mimic that even in other programming languages, let alone the wider tool ecosystem. A few people, here and there, put in some effort, but nothing at scale.
For Rust this work was imperative because their slogan is "A language empowering everyone to build reliable and efficient software" not "A language with terrible error messages that only nerds can handle" so I'm not surprised other people weren't doing this before Rust showed how much difference it makes, but I was surprised they didn't learn from that.
I hope it burns with fiery hot flames.
Teams is not quite as bad in terms of stability. The UX and performance are terrible though.
Yet.
The PWA is ass.
i guess "just" the MS Teams website has an issue?
https://www.statista.com/statistics/1033742/worldwide-micros...
are there any new updates on this rewrite?
Re: sibling comment: I'm European, not native English speaker.
HN is lucky to have so many non-native English speakers and they/you are all welcome here. We don't let HN users criticize others for their English - especially since most of the rest of us have no second language at all.
Published Time: 6/28/2023 7:50:04 AM
Current status: We’re reviewing a recent configuration change which may have unexpectedly resulted in impact. We’re determining our next steps to resolve the impact.
This quick update is designed to give the latest information on this issue.
Published Time: 6/28/2023 7:17:19 AM
Title: Users may be unable to access the Microsoft Teams service
User impact: Users may be unable to access the Microsoft Teams service.
More info: Users may be unable to load Microsoft Teams via the "teams.microsoft.com" web page and desktop app.
Users may see an “Operation failed with unexpected error” message.
While we're focused on remediation, users with access to a desktop build that is cached, may not experience the impact.
Current status: We’re reviewing application logs to identify the root cause and determine a mitigation plan.
Scope of impact: Impact is specific to users who are served through the affected infrastructure and are not using a cached desktop build.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
Published Time: 6/28/2023 6:43:01 AM
Title: Users may be unable to access Microsoft Teams using web browsers
User impact: Users may be unable to access Microsoft Teams using web browsers.
More info: Specifically, users may be unable to load the "teams.microsoft.com" web page and see the error message "Operation failed with unexpected error."
Current status: We're reviewing service monitoring telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to any user who is served through the affected infrastructure.
Next update by: Wednesday, June 28, 2023, at 2:00 PM UTC
There’s an effectively-secret deployment of Mattermost Cloud for the “teams without whom the company cannot exist”.
Anything official that needs to be shared and recorded for the company or requires widespread notification is through Teams, but then individuals are all using their own apps and management thinks Teams satisfaction is above 90% according to some surveys that no one I've talked to has filled out.