Thanks for reporting, Shy! Looks like you’re not the only one who’s come across this. The bug is being tracked and we will let you know once it’s fixed.
This issue was resolved in the January release (24.01.1). If you continue to experience the issue, please reply to this topic for a team member to assist.