@Andrew_Davidson I can see from status page that this was resolved on May 10th but can it be a recurrent issue?
