This should be fixed in the next content update.