Hi Jai,
thanks for the Info - I did as you recommended :)
For future visitors or other people following this topic:
--
The reported issue is fixed in our latest build which is yet to release.
--
So this problem should be fixed with the next release/follower
to build #91085.