Hey @rupashri
Could you try the workaround steps here?
I do think we might have a bug on our hands, would like to have a second confirmation that this fixes the issue!