This issue was caused due to some content management system licensing issues.
Once identified, changes were put in place to enable the site’s functionality across our web farm.
Work is in progress to update and expand our licensing model across all application nodes to prevent any similar future issues.