Thanks all, this would be the same issue reported here, and we’re on the case:
Apologies for the confusion!