Hi, @Suedkiez, thank you for your post, it was supposed to address this:
But it was not a 100% reliable fix, and the QA has not been able to replicate this issue locally before the release, so I believe, our dev team will need to take another look at this problem.