Azure Static Web App - Deployment Failure after timeout

Question

Azure Static Web App - Deployment Failure after timeout

David Anstee 5

Summary: We are experiencing repeated deployment failures when deploying our Azure Static Web App (SWA) via GitHub Actions. The deployment process completes the build, zipping, and upload stages successfully but fails during the Azure Functions deployment phase with the message:

Deployment Failed :( Deployment Failure Reason: Failed to deploy the Azure Functions.

This occurs consistently on one environment (Admin Test – Standard plan), while other environments (Assist Dev, Assist Test, and Admin Dev – Free plan) deploy successfully.

Technical details:

Function runtime: .NET 8 (Functions Runtime ~4)

OS: Linux

Build tool: Oryx (latest image, automatic detection)

GitHub Action: Azure/static-web-apps-deploy@v1

Deployment logs show normal progress for build, zipping, and upload, followed by repeated “InProgress” polling before timeout and failure (~120 seconds).

Even after removing all functions from the app, the deployment still fails at the same point.

The issue appears unrelated to Node warnings — our API is built in .NET, not Node.

We suspect this may be an Azure-side timeout or service issue within SWA’s function deployment pipeline. We need assistance identifying why Azure Static Web Apps is timing out during the “Deploy Azure Functions” phase, even when no functions are present. Specifically, we’d like to know:
- What component or validation step could be stalling the deployment process?
- Are there known timeouts, resource limits, or recent platform changes affecting .NET 8 Function Apps in SWA?
- How can we retrieve more detailed diagnostic logs from the Azure side to pinpoint the cause?

Anonymous

2025-11-10T10:12:28.6666667+00:00
Hi @David Anstee

Thank you for posting your question on Microsoft Q&A.

In the Standard plan, Azure Static Web Apps always sets up a dedicated Azure Functions host for APIs, even if your app does not have any functions. Because of this, the “Deploy Azure Functions” step still runs and waits for the Functions host to start. If there is no API, this step may keep waiting until it times out.

In the Free plan, deployments use a shared environment. If no API is found, it usually skips this step, so the deployment finishes successfully.

To fix this, please update your GitHub Actions workflow:

Remove or leave the api_location setting empty for your Admin Test environment.

Add this line to skip the API deployment step: skip_api_build: true

This will tell Azure Static Web Apps not to deploy or warm up any Functions host when there is no API.

You can find more details in the official documentation: Azure Static Web Apps GitHub Actions workflow configuration

Feel free to post back if you have any more questions or need further help.
Jack Stephenson 0 Reputation points

2025-11-10T12:56:29.5166667+00:00

@Vimal Lalani you are not adressing the question in any practical way.

Our SWA has an API layer. So, whereas disabling the API for the deploy may avoid the timeout.
It would leave our application crippled, as the API is a key part of the functionality.

We need to know why it is timing out?
What is going on?
Yes we temporarily removed the functions from our API to see what impact that would have.
And still we get a timeout.

There are no meaninngfull logs produced on the Azure side to tell us what is happening.
That is why we are reaching out to you.

Moreover, we have a similar SWA, with APIs and it is working in a standard deployment.

For use this is a high priority blocker.

We are building ok.
We are zipping ok
We are uploading ok
Then stalling when Azure starts the SWA

2025-11-08T08:54:00.9245217Z [32mFinished Upload. Polling on deployment.[0m 2025-11-08T08:54:01.0478047Z [37mStatus: InProgress. Time: 0.1230665(s)[0m 2025-11-08T08:54:16.2573007Z [37mStatus: InProgress. Time: 15.3325483(s)[0m 2025-11-08T08:54:31.4273213Z [37mStatus: InProgress. Time: 30.502535(s)[0m 2025-11-08T08:54:46.9485372Z [37mStatus: InProgress. Time: 46.0240586(s)[0m 2025-11-08T08:55:02.3315138Z [37mStatus: Failed. Time: 61.4053886(s)[0m 2025-11-08T08:55:02.3318235Z [31mDeployment Failed :([0m 2025-11-08T08:55:02.3344024Z [31mDeployment Failure Reason: Failed to deploy the Azure Functions.[0m

Please advise on how he can
a) Understand what is causing the timeout
b) How we can avoid it
Jack Stephenson 0 Reputation points

2025-11-10T13:04:03.4066667+00:00

We tried to upen a support ticket. BUt it took us here.

How do we open a ticket.
Jack Stephenson 0 Reputation points

2025-11-10T13:15:29.9866667+00:00

@Vimal Lalani I just re-read this, and I must say I find your response extremely disrespectful and totally lacking empathy for our situation.

We are having issues deploying APIs to the SWA.

Your solution. Turn off deployment of APIs/

And you finish by saying. reach out if there is anything else I can help with.

I am not sure if you are being sarcastic or ironic.

But this is not the level of support we expect from Microsoft.
Jack Stephenson 0 Reputation points

2025-11-10T13:18:35.6333333+00:00

@Vimal Lalani I just re-read this, and I must say I find your response extremely disrespectful and totally lacking empathy for our situation.

We are having issues deploying APIs to the SWA.

Your solution. Turn off deployment of APIs/

And you finish by saying. reach out if there is anything else I can help with.

I am not sure if you are being sarcastic or ironic.

But this is not the level of support we expect from Microsoft.
Anonymous

2025-11-10T13:28:43.2233333+00:00

Hi @Jack Stephenson / @David Anstee

Could you please share details asked over private message for further review?
Anonymous

2025-11-11T08:30:28.1433333+00:00

Hi @Jack Stephenson / @David Anstee

Thank you for sharing your feedback — I truly apologize if my previous response came across as dismissive or lacking empathy. That was certainly not my intention.

As I understand it work in other environments. To clarify, my earlier suggestion about skip_api_build: true was meant as a temporary troubleshooting step to help confirm whether the timeout was related to the Functions deployment pipeline itself, not as a recommendation to disable your API permanently.

Since your deployment does include APIs, let’s focus on addressing the root cause of the timeout.

Test with a minimal API – Try deploying a minimal test Function (like a simple “Hello World”) to see if the Functions host initializes successfully. If this works, the issue could relate to the project structure or startup configuration in your .NET function app.

Moreover, if you share asked detail over private message, we'll be happy to assist you further.
Anonymous

2025-11-12T13:21:50.01+00:00

Hi @Jack Stephenson / @David Anstee

Have you identified the root cause of the deployment failure. If the issue is resolved on your end, you're welcome to share the resolution.

Your answer

Anonymous

2025-11-10T10:12:28.6666667+00:00

Hi @David Anstee

Thank you for posting your question on Microsoft Q&A.

In the Standard plan, Azure Static Web Apps always sets up a dedicated Azure Functions host for APIs, even if your app does not have any functions. Because of this, the “Deploy Azure Functions” step still runs and waits for the Functions host to start. If there is no API, this step may keep waiting until it times out.

In the Free plan, deployments use a shared environment. If no API is found, it usually skips this step, so the deployment finishes successfully.

To fix this, please update your GitHub Actions workflow:

Remove or leave the api_location setting empty for your Admin Test environment.

Add this line to skip the API deployment step: skip_api_build: true

This will tell Azure Static Web Apps not to deploy or warm up any Functions host when there is no API.

You can find more details in the official documentation: Azure Static Web Apps GitHub Actions workflow configuration

Feel free to post back if you have any more questions or need further help.
Jack Stephenson 0 Reputation points

2025-11-10T12:56:29.5166667+00:00

@Vimal Lalani you are not adressing the question in any practical way.

Our SWA has an API layer. So, whereas disabling the API for the deploy may avoid the timeout.
It would leave our application crippled, as the API is a key part of the functionality.

We need to know why it is timing out?
What is going on?
Yes we temporarily removed the functions from our API to see what impact that would have.
And still we get a timeout.

There are no meaninngfull logs produced on the Azure side to tell us what is happening.
That is why we are reaching out to you.

Moreover, we have a similar SWA, with APIs and it is working in a standard deployment.

For use this is a high priority blocker.

We are building ok.
We are zipping ok
We are uploading ok
Then stalling when Azure starts the SWA

2025-11-08T08:54:00.9245217Z [32mFinished Upload. Polling on deployment.[0m 2025-11-08T08:54:01.0478047Z [37mStatus: InProgress. Time: 0.1230665(s)[0m 2025-11-08T08:54:16.2573007Z [37mStatus: InProgress. Time: 15.3325483(s)[0m 2025-11-08T08:54:31.4273213Z [37mStatus: InProgress. Time: 30.502535(s)[0m 2025-11-08T08:54:46.9485372Z [37mStatus: InProgress. Time: 46.0240586(s)[0m 2025-11-08T08:55:02.3315138Z [37mStatus: Failed. Time: 61.4053886(s)[0m 2025-11-08T08:55:02.3318235Z [31mDeployment Failed :([0m 2025-11-08T08:55:02.3344024Z [31mDeployment Failure Reason: Failed to deploy the Azure Functions.[0m

Please advise on how he can
a) Understand what is causing the timeout
b) How we can avoid it
Jack Stephenson 0 Reputation points

2025-11-10T13:04:03.4066667+00:00

We tried to upen a support ticket. BUt it took us here.

How do we open a ticket.
Jack Stephenson 0 Reputation points

2025-11-10T13:15:29.9866667+00:00

@Vimal Lalani I just re-read this, and I must say I find your response extremely disrespectful and totally lacking empathy for our situation.

We are having issues deploying APIs to the SWA.

Your solution. Turn off deployment of APIs/

And you finish by saying. reach out if there is anything else I can help with.

I am not sure if you are being sarcastic or ironic.

But this is not the level of support we expect from Microsoft.
Jack Stephenson 0 Reputation points

2025-11-10T13:18:35.6333333+00:00

@Vimal Lalani I just re-read this, and I must say I find your response extremely disrespectful and totally lacking empathy for our situation.

We are having issues deploying APIs to the SWA.

Your solution. Turn off deployment of APIs/

And you finish by saying. reach out if there is anything else I can help with.

I am not sure if you are being sarcastic or ironic.

But this is not the level of support we expect from Microsoft.
Anonymous

2025-11-10T13:28:43.2233333+00:00

Hi @Jack Stephenson / @David Anstee

Could you please share details asked over private message for further review?
Anonymous

2025-11-11T08:30:28.1433333+00:00

Hi @Jack Stephenson / @David Anstee

Thank you for sharing your feedback — I truly apologize if my previous response came across as dismissive or lacking empathy. That was certainly not my intention.

As I understand it work in other environments. To clarify, my earlier suggestion about skip_api_build: true was meant as a temporary troubleshooting step to help confirm whether the timeout was related to the Functions deployment pipeline itself, not as a recommendation to disable your API permanently.

Since your deployment does include APIs, let’s focus on addressing the root cause of the timeout.

Test with a minimal API – Try deploying a minimal test Function (like a simple “Hello World”) to see if the Functions host initializes successfully. If this works, the issue could relate to the project structure or startup configuration in your .NET function app.

Moreover, if you share asked detail over private message, we'll be happy to assist you further.
Anonymous

2025-11-12T13:21:50.01+00:00

Hi @Jack Stephenson / @David Anstee

Have you identified the root cause of the deployment failure. If the issue is resolved on your end, you're welcome to share the resolution.