Thank you for reporting this! I’ve found the issue and it is now fixed internally.