Hi @rTeuty, thanks for letting us know! We are aware of the issue, and we already have an update in the works to address it.