Thanks for reporting this. The team is able to reproduce this and is working on fixing it now.