almost 4 years ago - Ignasis - Direct link

Hey @Narelle

Thanks for the feedback. We’re aware of this issue and it’s been fixed internally, pending review and testing. It’s currently scheduled for release 2.3.