It was a solution to an old problem which currently is not a problem anymore.
We have been working towards revamping the system since the beginning the year to better accomodate the operations and problems WK faces today. Yesterday’s update was a major one since we switched reads over to a new model (Improved response times, especially for API, some bugs appeared, but were addressed shortly after). Eventually we will get rid of the async. But one step at a time 
I forgot about the time difference, although it’s in the afternoon here when it happened to me, it was still morning there where you are haha.