Slot Content Fetch internal errors

We identified the root cause to be related to the recent addition of an US region to our services. Our token validation was incorrectly wired on the new global API.

The issue has been resolved, but we’ll continue monitoring the new API’s behavior.

We have confirmed that the issue relates to our recently updated token system.

Only customers using server-side token signatures are affected.

We have detected internal errors affecting the personalized slot contents of some customers. We are investigating the cause of those errors.