Anyone else get this error message?

Thanks for the tag! Other users have reported this to our team as well; we have an open investigation for it with our engineering team, who are working to resolve it as soon as possible.

1 Like