Hi @KM1543 and all,

There is another thread on this issue where I commented that we fixed the issue and it will be included in the next beta deploy and the production deploy after that. You can see more information in my reply on the other thread or in the deploy notes which will be published on October 11th.