​@Mikita - thank you for reporting this issue. There is an existing thread in which we are already tracking this bug so I recommend keeping an eye for any updates there: 

Thank you!