Seems like that might be related to our in-progress migration, @thewellington :
I’ve alerted the team who will try to work on a fix as soon as the migration is complete.