Thank you! This specific bug is already being tracked by the team – we’ll update when a fix becomes available