Nev

Hi @jpalmowski, sorry for the delay. As you have already seen, looking into the code the retry backoff should be kicking in to delay the retry operation (based on your...

Hi @itpropro, Sorry, No we have not scheduled this work yet so I don't have a possible ETA and the person how was originally allocated to this plugin is no...

@mRowlinson27 VERY nice find... I've created a new issue for this specific bug.

Hi @h0wXD, looking at your workaround and the actual code for the `stopTrackPage` they appear to be doing the same thing... Where the `stopTrackPage` calls the [`stop` action on the...

Thanks @pl-jcarter that is a REALLY good catch!!! -- BUT!!! We recently (Monday Feb 7, 2022) identified a change with the backed "Portal" that "stopped" adjusting the envelope.time for the...

The stopTrackPage takes 2 arguments that are key `_self.stopTrackPage = (name?: string, url?: string, properties?: { [key: string]: string }, measurement?: { [key: string]: number }) => {` The `name`...

@Karlie-777 can you please investigate this a bit more as I believe the start / stop should work in this case and please provide any other context you have for...

When you use a connectionString a valid instrumentationKey should still be included in that string, so passing an invalid or incomplete connection string will trigger this generic message. eg. `InstrumentationKey=xxxxxxxx-xxxx-xxxx-xxxx-000000000000;IngestionEndpoint=https://southcentralus-0.in.applicationinsights.azure.com/`...

Thats not going to work. Updating the config after passing it into the SDK is not supported, you need to set the config values before passing into the SDK. In...

Well technically (at least currently -- I've not completely finalized the config changes for updating yet), if you pass in an Object as the config you __should__ be able to...