Hi,

that’s a bug. We apologize for that, working on fixing this issue.