Hello @DRAGAN. Thanks for reporting this issue. We are aware of this and the team is working to fix that ASAP.