While we’re happy that this has worked for a few of you, it looks like this fix is not consistent from replies. As a reminder, this is a bug that we should have fixed yesterday. Please keep an eye on this thread and contribute logs to our information gathering email if the problem occurred again today.
I’m locking this thread to ensure we keep all reports in the correct location.