Hey there,
As @Narelle pointed out above, we’re aware of this issue and we’re working on a fix.
We’ll proceed to close the thread as it steered into some less-than-constructive conversation.
Apologies for the frustration this issue may cause, and thanks for the feedback.