We are currently evaluating this issue and will update this article when we haven more information.

In the interim, logging out of Web Portal and logging back in resolves the error.