Hi @MoNurk
This might have been reported again a few days later and fixed:
Have you tried again recently?