First time I’ve gotten this error, starting a new chat first doesn't fix it
Seem to fix itself, interesting never had to deal with that before
That was a backend issue, we fixed it on our side :)
· Sign up or log in to comment