Hello @Lastianseth, we’re aware of this issue and it’s being looked into by the team, apologies for the frustration.