@Abhay Chandramouli Thanks for your patience on this.
Upon investigating deeper, our engineering team confirmed that this is a bug, and a fix has been created which will be available in next three weeks (No exact ETA timeline might vary due to circumstances).
Here is the GitHub bug issue #2618 for your reference.
Feel free to reach back to me if you have any further questions on this.