We've taken care of this via a support ticket. Looks like there was some data issues in several areas that need to be addressed manually.