Same issue here! When can we expect it to be resolved?
Same here!! I hope it gets resolved soon
It’s fixed! Or at least, it’s fixed on my end. Full refresh the page if you’ve left it open, just to be safe.
Hey all, apologies for a 2nd issue in as many weeks here.
Whilst it presented the same, it was slightly different. Along with the fix for last weeks outage we pushed a big update to core packages in the backend. Some things you’ll notice, but lots of things that you don’t see - security patches and version bumps to keep it humming along, as well as prepping for future functionality. This bug got introduced at that point and was only impacting a subset of users which is how it made it through our QA and into production.
Again, we’ll be looking at what happened and how we can strengthen our processes to reduce the chance it happens again.
If you’re still seeing the issue please first hit Ctrl + Shift + R to do a “hard refresh” of the page. Then ping us if that didn’t solve it.
2 Likes
Paired device. Thank you!
1 Like
I just had same issue but found this thread and ctrl-shift-r cured it