Hi Shichao,
This is a known bug. You may also find this related thread helpful, where we confirmed this as a regression specific to the 04.17 build. Our team is actively working on a fix.
We’ll update this area once a fix ships. @Tyson_Cai, this applies to your case as well.