Hi All, wanted to touchbase here. We have checked in with the dev team related to this issue. They are aware of the issue and have identified a fix. The team is working on a fix now and will be included in a future incremental. Timing is still being worked on for which incremental, but we should have more info on that over the next few weeks once the fix is finalized. Thanks, all.