Yeah, it's a problem.
After the scheduled site maintenance, the tech team unfortunately broke a few things in the backend. We attempted to get the feature somehow fixed, but after it was posted, there was no way for us to get into the feature to change it outside of the tech team going in...