We have identified this error to be the regression of a recent deployment, which has been reversed. This issue is now resolved.

If you see any ongoing issues that appear related to this, please submit a support ticket and we will investigate further!