Hi, we are still actively investigating this issue, and it's currently one of our top priorities. We're aiming to hotfix tomorrow to add some logging that will help us track down the root of the bug more effectively. We will release a fix as soon as we possibly can once we have the info we need from that logging. I will let everyone know as soon as I hear anything on the status of a fix after that logging is implemented.