Hi @CSAle & @VivienTang, Thanks again for reporting the issue; it should be fixed now. Apologies for the inconvenience!