This issue is now resolved.

If you are still seeing this issue, Contact Support and reference this article. .