I also just found out that this is a known issue which came up in an earlier post:
Our engineering team has a Jira to get this fixed.
Thanks,