This issue was fixed, i believe, at least a week ago. Another user had previously alerted me to the fact that it was working:
@RobWilk, our internal alert indicates that this issue is still open and ongoing.
That said, we appreciate you letting us know that it appears to be resolved on your end!