Microsoft Teams: Notifications can arouse Apple Watch sleepers

Sleeping tracking with the Apple Watch makes sense, so the computer clock can capture the temperature, the heart rate and – since Watchos 11 on certain models – also sleep apnea. The Apple Watch uses one to match sleep tracking so -called slap coat. This sends both watches and the iPhone coupled with it to the resting banks at a certain time. You can set which apps should also be reduced to the watch during the bedtime. Alternatively, you can only exclude certain apps or, instead of individual apps, also define a group of people that may or not. Telephony applications must also be controlled. The problem: Because of bugs – or possibly even wanted – some apps do not stick to the slap. A current case that the Mac & I editor has experienced is Microsoft Teams: It also aroused users with a watch vibration if it wasn’t allowed. Confusingly, the problem does not occur with all users and sometimes only sporadically. After all, there is a way to prevent it.

I want to score, but not teams

An example: the sleep coat runs until 7 a.m. Then both iPhone and Apple Watch (which reflects the notifications of the iPhone) should remain calm up to that time. Apple intelligence prioritization or automatic focus mode have been switched off, as well as time-critical news (whereby these are not sent by teams at least according to the notification settings). Nevertheless, a message from a colleague is in 6 a.m. 57 who did not even write to those affected directly. Instead, it is a “@Channel” mention. Another team problem applies here: The application does not allow it to mute “@Channel” mentions per channel-you can only deactivate them in general, which you do not necessarily want (in the desktop version there is a setting Pro Channel / Team).

But even if this was possible, the notification during the slap focus should not go through because this team is not explicitly allowed. This works over several days, teams always penetrate. At the same time, we found that Apple itself has a bug in the slap focus: if you expand the sleeping period for the current day at short notice (for example on weekends), you will be awakened later, but notifications will be resumed at the original time of the end of the sleep. With the result that of course you will be awakened again.

Traceability just semi

The problem with the problem: we did not see it on one iPhone, on another – which, however, had a very own configuration – in a trial run. This remains the assumption that Microsoft deals with the slap coat restrictions with any tricks: This remains: a guess. However, it has been known for several years that teams can penetrate the flapokusfor example for calls. So far, it has not been cleared up why this happens. Affected people report on a problem that lasted for years, which is also Ignore in the official Microsoft Forum became.

Ultimately, our solution to the team sleep disorder was to use the resting function built into teams themselves that can be found under your own avatar and the settings. There you can define a quiet time in which teams should no longer be notified. A period of time can be selected here, for example 10 p.m. to 7 a.m. In our attempt it actually worked: only after the end of time did notifications go back. Even more confusing: When we switched off the Quiet-Time again to check whether the sleep coat was still disturbed, this suddenly no longer happened the following morning. We will continue to pursue the phenomenon and update this post if necessary.