Hello,

Thanks for reporting the issue. Unfortunately, there is nothing we can do about this at the moment.

This should hopefully be corrected when we’ll perform a database update at the beginning of February.

Regards.