@Newcastle1 This was suggested by our development team as a workaround. I would suggest waiting; our team is working to get this issue resolved. Once it is resolved, we will update you in this thread. We appreciate your patience.
