Nev

@nika1001 FYI - the fix is now checked in and the automated pre-release night build has been published with #1900, so you should be able to pre-validate that this fixes...

Yes you can, as long as all of the subscription(s) all end up in the same region (and therefore get sent to the same location -- without the server sending...

Just fixed up the "location" of the name config in the above as it should be at the same level as cfg (doh!) just as is documented in the main...

@FredUK, and just to circle back on your options (sorry I was out last week). 1) @Karlie-777 found a race condition in the way the scripts are loaded and initializing...

Hi @FredUK, The OnInit, needs to be outside of the cfg: {} as it's a snippet config value and not the AI config. I changed your jsFiddle for the 1st...

Ok, a CORB error is a little tricky to diagnose as it's going to depend on what the server returned in the body of the response and the Content-Type header....

@FredUK - excellent, I suspect it's something else in the response. I'm currently setting up an email alias that will enable you to send the trace (or a link) directly...

Thanks @FredUK, I'm reviewing the trace and while the response seems fine there are differences in the outbound request specifically the Content-Type which might be causing the issue -- investigating.

I've split out the CORB issue to #1653, as the requests that are returning the CORB issue appear to be originating from the _beaconSender() (using the sendBeacon API). Assuming this...

`appInsights.context.operation.id` is from v1 of the since v2 this is how its done https://docs.microsoft.com/en-us/azure/azure-monitor/app/javascript?tabs=snippet#advanced-correlation `appInsights.context.telemetryContext.parentID`