Thanks for flagging folks! A fix was rolled out for this yesterday - if you’re still seeing this, please let us know.