Thank you for identifying this issue. We are currently working on it and it will be fix trough a product update later today.