Forum Discussion
Brian Levenson
Microsoft
I apologize for the false resolution and have an update to provide. Late last week, we found that we were hitting a connection threshold, so we scaled out the system on Monday and immediately alleviated that problem. On Tuesday, we started experiencing new connection problems. The platform team is looking into this, and the Message Center team has set up monitoring. When we are alerted of connection problems, we cycle the APIs. In parallel, we are designing a more reliable solution, which is targeted for implementation this calendar year.
I'm not sure whether the Service Health Dashboard uses the same API and solution, but I'll ask the team to look into it.
Thanks for the ongoing feedback!
Deleted
Nov 21, 2016Just reconfirming that it's working for me, including on a brand new tenant that I set up yesterday,
However, what I do occasionally see is that the Message center tile on the root dashboard often reports (and displays) X unread messages, but when you drill into the Message center, the correct status is reported. This can be after having the correct status previously reported in the tile. It's like it's picking up it's data from different caches or something.
However, what I do occasionally see is that the Message center tile on the root dashboard often reports (and displays) X unread messages, but when you drill into the Message center, the correct status is reported. This can be after having the correct status previously reported in the tile. It's like it's picking up it's data from different caches or something.