Issue fully resolved. The incident happened because there was a deployment of a JS agent configuration to a subset of customers, which unfortunately contained a configuration bug. The change was cached at the CDN level and in the end-user browsers that caused the rollback take additional time. We truly apologize for this inconvenience.

We have fixed the root cause of the identification issue, however in the browsers that cached the JS agent it may take up to 60 minutes to start getting the updated script and identify normally.

We're still working on the issue resolution. We have performed a rollback of the most recent change and working on the rest of the dependencies.

identification is affected