Hey there @MartinWalker
Thanks for your feedback. This is a known issue and we’ll release a fix for it soon.