Hi Siju,

This is a known issue, and is caused by a mistake from our side

We will fix it as soon as possible