Hi Paris, I was able to confirm that an internal utility was causing this script to get loaded in twice to the page. Reducing this to a single load does appear to have resolved the issue with this status. Appreciate the quick feedback and support!

Thanks I’ll submit that to the feedback assistant. We did end up pinning to v1.3.7 for the time being.