Hi @drobinson
This is a known issue we’re in the process of researching.
We’ve not been able to replicate it, but if you can provide some additional info such as what operating system were you using (eg. MacOS 10.15.3) and which web browser were you using (eg. Chrome 79) it can help us with replicating the error.