Hey, thanks for the report. Here’s a similar topic. I’ve also logged the issue in our internal tracker and hope for a quick fix.