Hey @Jimoacha
We’re aware of this issue and our team is looking into it. Thanks for the feedback and apologies for the frustration.