Are you still using Microsoft Bot Framework State Service? You need to read this and act today!
If you’re still using the Microsoft Bot Framework State Service then hopefully you already know that it’s been depreciated, since December 2017.
Now, in a recent blog post, we’re getting confirmation that the service will be turned off for writes on May 21st 2018. Read operations will continue to be available until July 31st to give you a chance to grab data out of the service and migrate over.
Between now and then end of May, the service will gradually degrade in an attempt to bring attention to its impending demise:
- April 15 – April 30 : read and write calls will take longer to execute. This will gradually increase to up to 500ms.
- April 30 – May 20 : scheduled brownouts will occur at the top of each hour, from 5 up to 30 minutes. During the brownout, calls will apparently (according to the blog post) return the infamous HTTP 418 “I’m a teapot” status (yes, really).
- May 21st onwards: all write operations will be blocked.
If you’ve done nothing to migrate from the State Service, then you’ve got a few days before things start to slow down, but you should start implementing your own solution for managing state today if you want to avoid being impacted.