Azure Function Deployment Issue: [Kudu-RemoveWorkersStep] Fails with HttpClient.Timeout

Question

Azure Function Deployment Issue: [Kudu-RemoveWorkersStep] Fails with HttpClient.Timeout

Davydenko Vadym 5

I’m trying to publish a TypeScript Azure Function to a Function App running on Flex Consumption plan.

Inbound traffic to the Function App is disabled.
Outbound traffic goes into a VNET.
The storage account has public access disabled and Private Endpoint connected to the same VNET.

When deploying from local, both of the following commands lead to the same error logs:

func azure functionapp publish some-function-name --typescript

and

az functionapp deployment source config-zip \
  -g rg-abc \
  -n some-function-name \
  --src "path/to/zip" \
  --timeout 6000

Observed Behavior

Both commands generate nearly identical deployment logs and end with:

[Kudu-RemoveWorkersStep] starting.

Deployment was successful with Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

[2025-08-28T10:43:06.033Z] "Deployment was partially successful, Please check the printed logs.

When using func azure functionapp publish, the deployment actually succeeds (functions are published and run), even though the error is printed.
When using az functionapp deployment source config-zip, the deployment fails entirely (no functions deployed).

Full Log Snippet (from func azure functionapp publish):

func azure functionapp publish some-function-name --typescript
Getting site publishing info...
[2025-08-28T10:25:53.401Z] Starting the function app deployment...
[2025-08-28T10:25:53.406Z] Creating archive for current directory...
Uploading 60.69 MB [##############################################################################]
Deployment in progress, please wait...
Starting deployment pipeline.
[Kudu-SourcePackageUriDownloadStep] Skipping download. Zip package is present at /tmp/zipdeploy/b13b497c-c3fe-4f5c-a549-e714726624dc.zip
[Kudu-ValidationStep] starting.
[Kudu-ValidationStep] completed.
[Kudu-ExtractZipStep] starting.
[Kudu-ExtractZipStep] completed.
[Kudu-ContentValidationStep] starting.
[Kudu-ContentValidationStep] completed.
[Kudu-PreBuildValidationStep] Skipping pre-build validation (remotebuild = false).
[Kudu-OryxBuildStep] Skipping oryx build (remotebuild = false).
[Kudu-PostBuildValidationStep] starting.
[Kudu-PostBuildValidationStep] completed.
[Kudu-PackageZipStep] starting.
[Kudu-PackageZipStep] completed.
[Kudu-UploadPackageStep] starting.
[Kudu-UploadPackageStep] completed. Uploaded package to storage successfully.
[Kudu-RemoveWorkersStep] starting.
Deployment was successful with Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
[2025-08-28T10:43:06.033Z] "Deployment was partially successful, Please check the printed logs.

Does anyone know why this happens and how to fix it?

Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-08-28T13:38:18.6866667+00:00
Davydenko Vadym,

Here are a few steps and considerations that might help you resolve this:

Check Network Configurations: Given that your outbound traffic goes into a VNET and the storage account has a private endpoint, verify that all necessary networking configurations are correctly set up. Ensure that the Azure Functions app can communicate with the storage account and any other services it needs to access.

Deployment Size: The error can occur if your package size is too large for the Azure App Service plan in use. Consider checking your app's size and the configurations of the App Service to ensure you’re not running into resource limits. You could also try scaling your App Service Plan to accommodate higher resource demands.

Logging: Enable more detailed logs in Kudu to get a better insight into what might be causing the timeout. This can provide additional context on failures during the deployment process.

Retry the Deployment: Azure has known variability in deployment times; it can sometimes help to simply retry the deployment after ensuring that all configurations are correct.

Check Kudu Logs: Access the Kudu diagnostic logs by navigating to https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole. Look for any specific errors in the logs that are related to the deployment process.

If the steps above do not resolve the issue, consider these follow-up questions:

Have you recently updated any configurations in your Azure Function App or its networking settings?

Are there any other services or dependencies that your function app interacts with that could also be affected by the VNET settings?

Do you have any specific deployment steps or scripts that could be contributing to the issue?
Davydenko Vadym 5 Reputation points

2025-08-29T10:52:49.0233333+00:00
@Praveen Kumar Gudipudi
thanks for you response!

answering your questions:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-01T09:52:40.7533333+00:00

Davydenko Vadym,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Davydenko Vadym 5 Reputation points

2025-09-02T11:10:40.2066667+00:00
hey again, thanks for you response.
I actually answered, but my comment was deleted. :(
the answer:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.thanks for you response! answering your questions:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.

3 answers

Your answer

Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-08-28T13:38:18.6866667+00:00

Davydenko Vadym,

Here are a few steps and considerations that might help you resolve this:

Check Network Configurations: Given that your outbound traffic goes into a VNET and the storage account has a private endpoint, verify that all necessary networking configurations are correctly set up. Ensure that the Azure Functions app can communicate with the storage account and any other services it needs to access.

Deployment Size: The error can occur if your package size is too large for the Azure App Service plan in use. Consider checking your app's size and the configurations of the App Service to ensure you’re not running into resource limits. You could also try scaling your App Service Plan to accommodate higher resource demands.

Logging: Enable more detailed logs in Kudu to get a better insight into what might be causing the timeout. This can provide additional context on failures during the deployment process.

Retry the Deployment: Azure has known variability in deployment times; it can sometimes help to simply retry the deployment after ensuring that all configurations are correct.

Check Kudu Logs: Access the Kudu diagnostic logs by navigating to https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole. Look for any specific errors in the logs that are related to the deployment process.

If the steps above do not resolve the issue, consider these follow-up questions:

Have you recently updated any configurations in your Azure Function App or its networking settings?

Are there any other services or dependencies that your function app interacts with that could also be affected by the VNET settings?

Do you have any specific deployment steps or scripts that could be contributing to the issue?
Davydenko Vadym 5 Reputation points

2025-08-29T10:52:49.0233333+00:00

@Praveen Kumar Gudipudi
thanks for you response!

answering your questions:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2025-09-01T09:52:40.7533333+00:00

Davydenko Vadym,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Davydenko Vadym 5 Reputation points

2025-09-02T11:10:40.2066667+00:00

hey again, thanks for you response.
I actually answered, but my comment was deleted. :(
the answer:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.thanks for you response! answering your questions:

No changes in configurations.

There is also a KeyVault, but connection in Environment Variables of function app shown as "Resolved".

No scripts, I only use commands mentioned above.

about your suggestions:

Size of zip is 60 mb, so it's under the limit.- https://<your-function-app-name>.scm.azurewebsites.net/DebugConsole is not accessible for this function, returns 404.- Retry deployment doesn't help.- Networking seems to be good, because there are actual files being deployed in the blob storage and KV is fetched.

Answer 1

Davydenko Vadym 5

forgot to give my solution back in time, but I faced that issue again and the fix was: https://github.com/Azure/Azure-Functions/issues/2635#issuecomment-3788663697

0 comments

Answer 2

nikithakoshy 80

I have the same issue with the Flex consumption Function App, and removing the private endpoint resolved the problem. I also found that it was working fine before, and this issue has only recently started occurring.

0 comments

Answer 3

@Praveen Kumar Gudipudi Flex Consumption Plan doesn't support the debug console url.

I am starting to get similar error in the last few days while it has been working fine in the past.

If I remove the private endpoint for my function app, it works. So I think there is something wrong with my network/pe configurations.

search in (traces) "Kudu" and timestamp > ago(30m)

19/09/2025, 11:57:28.778 am

Deployment was successful with Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing. 19/09/2025, 11:52:24.761 am [Kudu-RemoveWorkersStep] starting. 19/09/2025, 11:52:24.750 am [Kudu-UploadPackageStep] completed. Uploaded package to storage successfully. 19/09/2025, 11:52:23.741 am [Kudu-UploadPackageStep] starting. 19/09/2025, 11:52:23.739 am [Kudu-PackageZipStep] completed. 19/09/2025, 11:52:21.423 am [Kudu-PackageZipStep] starting. 19/09/2025, 11:52:21.421 am [Kudu-PostBuildValidationStep] completed. 19/09/2025, 11:52:21.420 am [Kudu-PostBuildValidationStep] starting. 19/09/2025, 11:52:21.419 am [Kudu-OryxBuildStep] Skipping oryx build (remotebuild = false). 19/09/2025, 11:52:21.418 am [Kudu-PreBuildValidationStep] Skipping pre-build validation (remotebuild = false). 19/09/2025, 11:52:21.417 am [Kudu-ContentValidationStep] completed. 19/09/2025, 11:52:21.417 am [Kudu-ContentValidationStep] starting. 19/09/2025, 11:52:21.415 am [Kudu-ExtractZipStep] completed.

Related post: https://www.reddit.com/r/AZURE/comments/1nkrbzy/azure_flex_consumption_python_functions/