This has been resolved internally and will be included in our next patch, apologies for the inconvenience.