Same here, good that it has been noticed before so the team is probably on it. However it says this topic has been solved but the “additional detail” is that it is still happening so who flagged it as “solved”. I will re-scan the thread but seems that there is only a preliminary identification of the issue not a solution.