I asked their support about it and this was the answer:
Thanks for flagging this. We're aware of the error and trying to fix it - it requires input from both sides to fix so it's taking a little longer than something completely internal.