Forum Discussion

Gerald_Mathieu's avatar
Gerald_Mathieu
Brass Contributor
Feb 17, 2025

Inbox / Private messages broken on my profile

Hi,

I'm trying to get informations regarding a case I opened 2 months ago and they are sent through private messages I can't open.

I see that I have 97 unread messages but when I click on the icon, it just open the Inbox, try to load something for a while then just give up, leaving me there.

Before someone tries to tell me that this is a cookie or cache issue, it is happening on several browsers, using normal or InPrivate session and on multiple computers so the problem is not there.

After searching, it seems that I'm not the only one having this issue.
Could someone have a look at it so I can reply to the people from Microsoft asking me informations in PM and not forcing me to ping them on LinkedIn? 

Kr,
Gérald


community
Private Messaging

6 Replies

Sort By
  • Ramona_Maxwell's avatar
    Ramona_Maxwell
    Brass Contributor
    Apr 03, 2025

    Wonderful and thank you Allen 

    This is impacting me quite a bit right now. Do you know an approximate ETA for the next release?

  • jamereach66t's avatar
    jamereach66t
    Copper Contributor
    Apr 03, 2025

    Gérald. Since you've already ruled out browser and cache issues, it might be a server-side problem. Have you tried reaching out to Microsoft support directly or checking if there's a known issue reported on their status page?

  • Ramona_Maxwell's avatar
    Ramona_Maxwell
    Brass Contributor
    Apr 02, 2025

    I'm experiencing the same issue and tested on Firefox on Windows and on an iPad (normal and incognito) as well as on a fresh installation of Edge on a separate Windows machine. My screen looks identical to yours with the icon saying I can choose a message but no message list appears to pick from.Allen please respond.

    • Allen's avatar
      Allen
      Icon for Community Manager rankCommunity Manager
      Apr 03, 2025

      Ramona_Maxwell Gerald_Mathieu 

      Thank you for your report, we have had a handful of similar reports sent to us via email. The good news is engineering have developed a fix for it and it will be fixed in the next release. 

      We will of course update this thread once its fixed, unfortunately there is no workaround at the moment and so please accept my apologies for the inconvenience.

Resources