@nick We have deployed a (possible) fix now, can you please try again?