Some messages appear sent but don't show up for the recipient until much later or when they open the chat. Calls sometimes don't ring and only appear as missed calls. Could this be a service issue, and what should I check?
Teams messages and call notifications are arriving late. How do I narrow down the cause?
Answers
Start by comparing the desktop and web clients with the same accounts. Send a test message, note when it was sent and when it appeared, and try a test call. Also check whether opening the chat makes the message appear.
If restarting the desktop app helps, see how long the improvement lasts. That points to a useful client symptom, but it doesn't rule out a service problem, especially if the web client falls out of sync too.
Reply to this answer
Check the service health section in the Microsoft 365 admin portal for notices affecting your organization. A public status page or a spike in outage reports can be a clue, but neither proves that your particular issue is a confirmed incident.
If there's no matching notice and it keeps happening, open a support case. Include affected users, approximate times, delay lengths, client types and whether calls, messages or both are affected.
Reply to this answer
Don't assume every Microsoft issue happening at the same time has the same cause. Check how many users are affected and whether the problem follows an account across clients or is limited to a particular app. That gives support something more concrete than just a general outage report.
Reply to this answer
For anything time sensitive, use another way to reach people until you've confirmed calls and messages are coming through. A message marked as sent isn't much help if the recipient can't see it yet.
Reply to this answer
Add your answer
Answers are reviewed before publication.
5a~socketwicket_649:
Include the time zone with those timestamps too. It makes the examples easier to correlate with service events.