Teams chat is stuck loading
Find out whether one chat, every chat or your connection is affected.
Applies to: Teams desktop and web.
Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

What does the message mean?
Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.
| What you see | What it may indicate | What to check |
|---|---|---|
| Spinner or blank chat (symptom) | Chat content has not loaded. A spinner alone does not identify the cause. | Find out whether one chat, every chat or your connection is affected. |
| Message not sent / retry shown (wording varies) | Delivery was not confirmed. The recipient may not have it. | Check the message status before retrying. |
| No message at all | Problems can happen without any message. A blank screen or a missing control is still useful evidence. | Record the visible behaviour, the time and who is affected. Do not guess a code. |

Step-by-step checks
Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.
Check the scope
- Do this
- If responsive, open another existing chat without sending a test message.
- What you should see
- One chat fails or every chat fails.
- Then what?
- Record which. Do not resend messages whose delivery is uncertain.
Check your connection
- Do this
- Open a familiar work website in an approved browser.
- What you should see
- It loads or shows a connection problem.
- Then what?
- If other work sites fail too, use your internal connectivity process. Do not disable security tools.
Protect unsent text
- Do this
- Check for unsent drafts and for any active call, recording or upload.
- What you should see
- You know what a restart would interrupt.
- Then what?
- Do not restart if it would interrupt a meeting or lose text you cannot save safely.
Restart once if safe
- Do this
- Use the normal Teams Quit control, then reopen Teams. Compare the approved web client if it persists.
- What you should see
- Chats load or the issue remains.
- Then what?
- If it remains or Teams will not quit normally, contact IT. No cache deletion is needed.
When to stop and contact IT or the owner
- Work could be lost, or you cannot tell which version is current.
- The problem repeats, or a managed setting blocks you.
- A step would change production data, shared connections, permissions or security.
What to put in your support request
The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.
Microsoft reference
Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.
Related guides
Was this guide helpful? Leave feedback
Tell us what worked, what was unclear, or what is missing. Feedback is private and goes to The Workflow Lab for review. It is not shown publicly and is not an IT support request.
The Workflow Lab is independent of Microsoft and is not your employer’s service desk.