The root cause of this issue was a deployment mismatch. The spot client was on a newer version than our servers. We resolved the problem by deploying the latest version to our backend servers.
We will take steps to prevent this issue from occurring in the future by improving our deployment system. We are also improving our alerts to be notified of similar problems more quickly.