Hello @sathish_gadde, thank you for reporting this.
It seems that this was already reported and a fix is coming.