Quote Originally Posted by Bayohne View Post
Greetings,

The development team has confirmed the issue and we have some information to share:
Does that mean they're working on a fix for those of us getting the error without being anywhere near an instance? Or are they still only fixing instances?