Hi there, thanks for contacting the Community. This issue should now be resolved after our engineering team applied a fix a little bit earlier on.
