almost 4 years
ago -
FatsharkLev
-
Direct link
Thanks for the report @Romucha!
This error is usually a hiccup in the backend which should resolve itself, however, we are noticing it popping up more frequently at the moment. I’ve passed this information along to development to review.