Thomas Ardal

I don't think I can provide an invocation id. At least an invocation id is not logged alongside the log message. I seems to come through Microsoft.Extensions.Logging but not as...

@v-anvari I see. Here's an invocation id from North Europe: 4dd84024-8b2b-4d0c-9fe2-328ea326d1cd

@v-anvari Sure, I will try to ping the host. Do you have any documentation on how to do that?

Ah sorry. I think I found it here: https://docs.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal. I have the same function app deployed to two different regions. I'll try to set `FUNCTIONS_EXTENSION_VERSION` to `~3` on one of...

@v-anvari I think it's pretty safe to say that the problem disappears when pinning `3.1.4`. Since yesterday, the warning has been logged three times on the function app running `~3`...

Update: I have pinned all of my function apps to `3.1.4` now and haven't seen the warning since.

@v-anvari There's both a `3.3.0` and `3.3.1` available. Which one do you recommend me to try out?

@exhaler I'm currently running `3.1.4` on half of my apps and `3.3.1` on the other half. I'll write an update here tomorrow (if I remember it).

Quick update. None of my function apps have reported the warning since yesterday. I'll pin all of them to `3.3.1`. I think this will be my process going forward where...

@v-anvari I think the pin there is for any patch version of `3.1`. So, `~3.1` will allow automatic upgrades to `3.3.1`, `3.3.2`, etc. but not `3.4.0`. Or am I misunderstanding...