This issue was caused by a code regression in which an incorrect configuration was imported and used. The service in question was imported and mistakenly used on the wrong UI pipeline, causing these errors and our team reverted builds to remove the offending code change. No further action is required by our customer and we do not expect this issue to recur as we’ve flagged this release for internal review.