I apologize for the inconvenience this has caused. We are aware of the issue, and it has already been fixed internally. The fix is currently being validated through our testing stages. As the rollout timing varies for individual users, I cannot provide a definite timeline for when you will see the fix implemented.