SWA not serving all deployed files

[Skintkingle]

SWA hosting is causing files to 404.
If we try and redeploy the same commit that we deployed successfully on a previous date, then the build appears to be successful, but browsing to our SWA seems to cause random files to not be deployed, resulting in 404s and page load issues. We are deploying a Blazor app using the AzureStaticWebApp@0 task. at version 0.247.1. This version is UNCHANGED and so is not the tasks fault.

Without any way to browse the SWAs content from the portal. I'm unable to verify if these files actually exist. They have always existed before and we've not changed anything so my assumption is the SWA is at fault, not our files/deployment.

Initially raised here

To Reproduce
deploy using AzureStaticWebApp@0 to a SWA site in Azure.
Attempt to browse to the site after deployment
From dev tools, notice random 404s on files

Expected behavior
A fully working deployment of our SWA

Screenshots

Device info (if applicable):

• OS: Windows 11
• Browser Firefox, but also fails on chrome and Edge
• Version 131.0.3

[hunglng]

I also struggled a whole day for this, I am also using Balzor WASM and SWA in preview environment. Tried to delete slot and recreate with the same name will cause 404 for whole site.
After 1-2 hours, the site will up and run again without any changes. It looks like CDN issue but I used Free plan and don't have CDN setup

[Skintkingle]

FWIW We're also on the free plan. And we are deploying to a non-production environment. (an env called UAT)

[jonavask]

We're also experiencing the same problem - causing 404's on our named environments with certain files. We're using the standard plan with Enterprise-grade edge however seeing this across all environments regardless of plan.

This is a highly critical issue!

[valeriiavask]

worth mentioning that some files ARE available, while other files are NOT
also, the files that are not available, if you refresh many times, in some occasions you could get the file back (as if it's being load balanced, and you don't always get the same result)

[patlamontagne]

The problem seems to be resolved today. Anyone else can confirm?

[Skintkingle]

I can confirm I'm not seeing the same issue today. We left the SWA totally alone so something cloud-side must have changed to fix it.

[hunglng]

I don't encounter this issue today but still afraid if it can happend again, because I don't know the reason or any workaround for this.

[ui-jb]

We've been experiencing an issue like this right after deployment on our hybrid Next.js (app router) site. The issues either go away after a few minutes or go away after clicking on a few links.