There is an error under the "Functions" node for a function app which created with Flex Consumption (Preview) hosting plan

[v-ruizh]

OS: All
Build Version: v1.14.1-alpha.0
Regression: Not a Regression

Repro Steps:

1. Create a python function app with Flex Consumption (Preview) hosting plan and East US 2 EUAP location.
2. Expand the above function app -> Expand the "Functions" node.
3. Check whether there is no error under the "Functions" node.

Expect:
There is no error under the "Functions" node.

Actual:
There is an error under the "Functions" node.

[nturinski]

note to self: I think for flex consumption, they may have changed the functions API endpoint. I need to investigate that.

[nturinski]

Could you reconfirm this? I am able to see my http triggers under a flex plan:

[v-ruizh]

@nturinski This bug still reproduces on the latest build. I didn't deploy any function to the Flex Consumption (Preview) function app. Just create a new function app with Flex Consumption (Preview) hosting plan and expand the Functions node. An error occurs under the Functions node.

The function shows well after deploying a function project to the function app.

[nturinski]

This seems to clear up on its own after a while. I only see it reproduce for a newly created flex app, but when I check later, the list is empty as expected.

And actually, I just tried creating a new flex function app and it seems like it's okay now?

[v-ruizh]

This seems to clear up on its own after a while. I only see it reproduce for a newly created flex app, but when I check later, the list is empty as expected.

And actually, I just tried creating a new flex function app and it seems like it's okay now?

I encountered this case you saw one time when testing Flex Consumption (Preview) at the first time, but it doesn't work well for all function apps with Flex Consumption (Preview).

Verified this bug on the latest main branch Functions extension build again, this bug still reproduces. The error will not disappear after a while, even though the error still exists when checking it the second day.