Forum Discussion
Delay in Teams Proactive Notification Popups (Internal and Customer Impact)
We are currently experiencing an issue with Microsoft Teams, both internally and among our customers. Specifically, there is a noticeable delay in the appearance of proactive notification popups. In many instances, these notifications are delayed by approximately 5 to 10 seconds after the triggering event using ms botframework sdk.
This issue affects the responsiveness of our Teams-based applications and workflows, particularly in time-sensitive use cases. The delay has been observed consistently across different environments, which suggests it may not be limited to a specific configuration or network.
We would appreciate your assistance in investigating this matter. If there are any known issues, recommended diagnostics, or configuration adjustments that could help mitigate this behavior, we would be grateful for your guidance.
Thank you very much for your support.
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.
6 Replies
KARAN_SHEWALE0525Microsoft
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 LearnClarification 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,
KaranIf 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.
- KARAN_SHEWALE0525
Thanks for bringing this issue to our attention. We will check and update you soon.
- KARAN_SHEWALE0525
Hi james099,
Thank you for reporting the delay in Teams proactive notification popups. Some delay is expected due to Teams client and service-side processing (official docs).
Recommended Actions:
- Ensure your bot and Teams client are up to date.
- Use action.execute in adaptive cards for better responsiveness (adaptive cards docs).
- Review
- Monitor Teams logs (Ctrl+Alt+Shift+1).
- If the issue persists, open a support ticket with Microsoft.
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/CopilotDevCommunityResponsesFeedback) link. Click here to escalate.
Hi Karan
Thank you for your response.
Could you please resend the link referenced in the sentence "Some delay is expected due to Teams client and service-side processing (official docs)."? The link appears to be broken or inaccessible on my end.
Additionally, I’d appreciate some clarification regarding the expected delay. In our case, when we send proactive notifications to the Microsoft Teams server, we receive a 200 OK response almost instantly (within 1 second). However, the end user sees the message only after a delay of 10–30 seconds.
Given that Teams is generally considered a real-time communication tool, this delay seems unusually long. Could you provide any insights into what might be causing this or what the typical delay range is?
Thanks again for your support.
Best regards,
