Because it wasn’t a bug, it was a consequence of some re-architecture. We couldn’t roll it back without breaking lots of other stuff, so we had to push forward with a refinement to the new approach. I explained the architectural change in detail higher up in this topic.
It’s in QA testing now, and going well. It will be out soon.