Hi @ramkumarr,
Welcome to our forum. 
As mentioned by @dineshh, this is a known issue, and our Product team is working on a fix to be released soon as we speak.
In the meantime, you can try one of the workaround detailed by @Elly_Tran below:
We hope this helps. Thanks.