Hey @K_Anudeep ,

 

Thanks for letting us know that this is a bug and is mitigated. I tried testing it  today again as i was getting the same error last week but it doesn't occur now anymore