Hi @Musicalman, thanks for your post. Yes, unfortunately this is still an issue we’re investigating. Just to clarify, a fix for this wasn’t announced as part of the 3.1 update, but it’s something that remains on our radar. Appreciate your patience in the meantime. Cheers.