Forum Discussion
Delay in Teams Proactive Notification Popups (Internal and Customer Impact)
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.
MicrosoftHi 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,
- KARAN_SHEWALE0525
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 Karan,
Thank you for your response.
Unfortunately, the official Microsoft documentation you provided does not mention any delays related to this issue. I am urgently trying to resolve this matter, as it is directly affecting my clients.
The troubleshooting steps you suggested have not resolved the problem. The Teams client is already up to date, and rate limiting has been properly implemented as per the guidelines.
Could you please escalate this case or provide more specific guidance or documentation that addresses this scenario?
Thank you for your continued support.
Best Regards