Hello All,
Thanks for the reports. We have a fix making its way through the pipeline regarding this bug, it is expected to be released with our next production build. There are no further details needed at this time, so I will go ahead and mark this thread for closure. Please keep an eye on our software release notes category for when the fix goes live. Thank you!