The issue was caused by a deployment configuration problem that prevented the Platform from fully accessing a required service. The configuration was restored, service was fully recovered, and additional safeguards have been implemented to prevent this issue from occurring in future deployments.
We apologize for any disruption this may have caused and appreciate your patience while the issue was resolved.