Hi Ian, I just wanted to followup here - At this time, we no ETA on when the fix for this issue will be rolled out. The issue is currently in our backlog and will be addressed in a future release. Thank you once again for bringing this to our attention - We really appreciate it