This issue should be rectified in a deployment we have planned for today.