This issue was due to some custom content management system scripts that were incorrectly excluded from the production feature updates under a newer release paradigm. The scripts were identified and deployed to resolve the issue.
The release team has identified the source of the issue and the scripts will be included in future releases to prevent a recurrence.