I reported a similar case in Early Release testing but it seems like it wasn’t yet fixed (or not completely fixed maybe) before the official release: