Hi @DiveLow . It looks like this is a known issue, and we’re looking into a solution. Thanks for the post.