Forum Discussion
Delay in Teams Proactive Notification Popups (Internal and Customer Impact)
- Jun 05, 2025
Hi James,
Thank you for your message.
Here is the official Microsoft documentation about proactive messaging and expected delays in Teams:
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/send-proactive-messages?tabs=dotnet#limitations-and-considerationsClarification on expected delay:
Normally, proactive messages in Teams should appear within a few seconds, but some delay can occur due to Teams client processing, background activity, or network conditions. Microsoft notes that delays are possible, especially if the Teams client is not active or is running in the background. A 10–30 second delay is longer than usual. Since your bot receives a 200 OK response quickly, the delay is likely happening on the Teams service or client side.What you can do:
- Make sure your Teams client and bot are up to date.
- Review Microsoft’s rate limits and throttling guidance.
- Test on different devices and networks.
- Use Teams logs (Ctrl+Alt+Shift+1) to check for errors.
- If the issue continues, please open a Microsoft support ticket with logs and timestamps for deeper investigation.
Let me know if you need more help or details.
Thanks,
Karan Shewale.
*************************************************************************
If the response is helpful, please click "**Accept Answer**" and upvote it. You can share your feedback via [Microsoft Teams Developer Feedback](https://aka.ms/DevSupportFeedback) link. Click [here](https://aka.ms/DevCommunityEscalationForm) to escalate.
Hi James,
Thank you for your follow-up.
Here is the correct link to the official Microsoft documentation on proactive messaging and its limitations:
Send proactive messages - Teams | Microsoft Learn
Clarification on Expected Delay:
Proactive messages in Teams are generally delivered within a few seconds. However, Microsoft notes that delays can occur due to several factors, including Teams client state (active, background, or offline), network latency, and service-side processing. While a short delay (a few seconds) is typical, a 10–30 second delay is longer than expected.
Since your bot receives a 200 OK response quickly, the delay is likely happening after the message leaves your service—either within the Teams service or on the client side. This can be influenced by:
- The Teams client being in the background or not actively running.
- Network or connectivity issues.
- Temporary service-side throttling or load.
Next Steps:
- Ensure both Teams client and bot are updated to the latest versions.
- Test across different devices, networks, and user accounts to rule out local issues.
- Review Limits and specifications for Microsoft Teams - Microsoft Teams | Microsoft Learn to ensure your bot isn’t being throttled.
- Collect Teams logs (Ctrl+Alt+Shift+1) and note timestamps of the delay.
If the issue persists and the delay is consistently 10–30 seconds, I recommend opening a Microsoft support ticket with detailed logs and timestamps for further investigation, as this is not typical behavior for Teams proactive messaging.
Let me know if you need any more details or assistance.
Best regards,
Karan
If this response is helpful, please click "Accept Answer" and upvote. For further feedback, you can use the Microsoft Teams Developer Feedback link or escalate via the Dev Community Escalation Form.