We are happy to report this issue is now resolved. If you are still experiencing this issue, please log a ticket via the Helpdesk.