You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Nodejs Http-trigger function with timeout issue when adding the VNet integration with default setting
Reproducing steps:
1.Create nodejs Http-trigger function in local and test without issue. (code is sample code, created by default)
2.Create nodejs (version 18) function app with EP1 plan. (OS: Windows)
Appsetting created by default as well.
3.Add VNet integration in this function app. (VNet is created via Portal by default setting without any custom configuration)
4.Use VS code to deploy nodejs function to Azure Function created by steps#2
The status of httpTrigger function is Enabled in Portal.
5.Invoke Http-trigger function URL, then getting timeout issue.
If disabling VNet integration, the Http-trigger function is back to normal.
The issue can be reproduced always once the VNet integration is enabled.
[ASK]
May I know how to mitigate the issue?
The text was updated successfully, but these errors were encountered:
Issue: Nodejs Http-trigger function with timeout issue when adding the VNet integration with default setting
Reproducing steps:
1.Create nodejs Http-trigger function in local and test without issue. (code is sample code, created by default)
2.Create nodejs (version 18) function app with EP1 plan. (OS: Windows)
Appsetting created by default as well.
3.Add VNet integration in this function app. (VNet is created via Portal by default setting without any custom configuration)
4.Use VS code to deploy nodejs function to Azure Function created by steps#2
The status of httpTrigger function is Enabled in Portal.
5.Invoke Http-trigger function URL, then getting timeout issue.
If disabling VNet integration, the Http-trigger function is back to normal.
The issue can be reproduced always once the VNet integration is enabled.
[ASK]
May I know how to mitigate the issue?
The text was updated successfully, but these errors were encountered: