Has anyone seen the issue resolved a UI reset? I know that was a recommendation this morning when the issue was first being reported here. However, with a bunch of reports now, and no indication that a UI reset is working, it’s been reported to our QA team for testing.