This is a known bug that the team is aware of. Thanks for checking in!