Hey @Fonse
This issue was reported earlier today (see here)
We’re working on a resolution - please don’t fear!