Hey @weezy2482
We’re aware of this issue and our team is currently looking into it. Apologies for the frustration.
We’re directing feedback about this issue on this other thread: