Welcome and thanks for posting in the Community, @sandra-edwards.
This has been reported as an ongoing issue and a ticket (INV-36469) was created and forwarded to our Product Engineers. They're now investigating the root cause of the issue and working to fix this as soon as possible.
In the meantime, I highly suggest contacting our Phone Support team so they can your details to our notification list. This will help our Engineers the number of users affected by the issue. An email notification will be sent to you once this has been resolved. I'll also inform you here when we get the update as well.