Confirming our QA team was able to reproduce this issue, and we've added it to our known issues list. Thank you for the reports, Tenno!