We believe this issue is resolved with our latest database update that was deployed a couple of hours (around 12:00 Eastern Time).   The "Update package version" is 1.0.75991.  If you do not have that (or newer), please choose "Check for updates". Please let us know if this resolves the problem for you.  Thank you again for your prompt feedback.
    • Like
    1