Microsoft Teams Microsoft Bot Framework

API outage: Bots posting typing indicators may receive 502s

As a part of our commitment to customers and Microsoft cloud services continuity during these unprecedented times, we’re making temporary adjustments to select capabilities within Microsoft 365. One of those adjustments is that we are temporarily scaling back typing indicators support in Teams. As a result bots posting typing indicators to users in the Europe region were receiving errors. To avoid polluting the logs for bots with errors, we have completed the world-wide rollout of a change to return HTTP 202 (Accepted) status-code when bots post typing indicators, even if the underlying typing indicator support is scaled back.

We are continuing to monitor our services on an ongoing basis and will share any further updates here.

Next update: April 14th.

Update on March 30th:

As a part of our commitment to customers and Microsoft cloud services continuity during these unprecedented times, we’re making temporary adjustments to select capabilities within Microsoft 365. One of those adjustments is that we are temporarily scaling back typing indicators support in Teams. As a result bots posting typing indicators to users in the Europe region were receiving errors. To avoid polluting the logs for bots with errors, we are now rolling out a change that will cause bots to receive HTTP 202 (Accepted) status-code when they post typing indicators, even if the underlying typing indicator support is scaled back.

We are continuing to monitor our services on an ongoing basis and will share any further updates here.

Next update: April 6th.

 

Original post:

As a part of our commitment to customers and Microsoft cloud services continuity during these unprecedented times, we’re making temporary adjustments to select capabilities within Microsoft 365. One of those adjustments is that we are temporarily scaling back typing indicators support in Teams. As a result bots posting typing indicators to users in the Europe region using any of the following values for ServiceUrl may receive errors and users may not see the typing indicators sent by bots.

  • https://smba.trafficmanager.net/emea/
  • https://smba.trafficmanager.net/uk/
  • https://smba.trafficmanager.net/fr/
  • https://smba.trafficmanager.net/de/
  • https://smba.trafficmanager.net/no/

As a bot developer, you may either modify your code to not use typing indicators for now, or ignore the errors encountered while sending typing indicators.

We are continuing to monitor our services on an ongoing basis and will share any further updates here. Next update: March 30th.

We’ll be sure to let the community know when we can restore full functionality to typing indicators.

Questions / Feedback: Please submit feedback on the GitHub page here. We’ll do our best to answer your questions quickly.

Stay informed: To stay up to date with API outages, you may subscribe to RSS feed here.

Leave a Reply

Your email address will not be published. Required fields are marked *

filter-icon