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
Describe the bug swa deploy times out after 300 seconds with the error message Failure during content distribution if the number of uploaded files surpasses ~3000 files.
To Reproduce
Steps to reproduce the behavior:
Produce more than 3000 files to upload to an SWA.
Execute swa deploy to deploy the 3000+ files.
Notice how Status: InProgress. Time: … is printed to the console 20 times.
Notice how the deployment ends after 5 minutes with the error message Failure during content distribution.
Expected behavior
I expect SWA to be able to upload more than ~3000 files. Either by allowing the timeout to be increased, or – preferably – by the SWA infrastructure simply working faster to distribute the files.
Screenshots
Desktop (please complete the following information):
I've been in touch with Microsoft Support regarding this issue, and after several weeks of back and forth it was identified and acknowledged with the following response:
Deployment with the provided project zip file: The deployment process is no longer getting stuck in the 80+ seconds between logging UTC time. The job-command is simply enumerating the files before proceeding to copy them as designed. The project files contain many directories with a small number of files in each.
Identified root cause and possible fix: The fix cannot be implemented quickly and will require longer-term planning.
The issue was then resolved with the following response:
In the meantime, it is recommended to reorganize the project files to reduce the number of subfolders.
We are working on a Dedicated SKU for Static Web Apps to more easily support customers with fine-grained control over settings that influence content distribution behavior. This new SKU will take the current issue into account.
Because of this, as well as Azure/static-web-apps#941 which has begun to rear its head with increasing frequency, we'll be migrating away from Azure SWA.
Describe the bug
swa deploy
times out after 300 seconds with the error messageFailure during content distribution
if the number of uploaded files surpasses ~3000 files.To Reproduce
Steps to reproduce the behavior:
swa deploy
to deploy the 3000+ files.Status: InProgress. Time: …
is printed to the console 20 times.Failure during content distribution
.Expected behavior
I expect SWA to be able to upload more than ~3000 files. Either by allowing the timeout to be increased, or – preferably – by the SWA infrastructure simply working faster to distribute the files.
Screenshots
![Deployment Failure Reason: Failure during content distribution.](https://private-user-images.githubusercontent.com/12283/342000349-2696a3e6-04c4-4d8b-a71a-3e74c7bfd7db.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2MDI1NzUsIm5iZiI6MTcyNTYwMjI3NSwicGF0aCI6Ii8xMjI4My8zNDIwMDAzNDktMjY5NmEzZTYtMDRjNC00ZDhiLWE3MWEtM2U3NGM3YmZkN2RiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA2VDA1NTc1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTcyYTI2NDJlNmNhY2MyZGM0MzQ0OTIzM2FjNzFlNjAwMTdhNTU2ZTc5NjdmMTBlN2NkMTE1YTM4NTVhZGY1MWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.oeJPcNhpYe3_ytlCqMV8hkTs3_qCDWMimA0fxKtZ_J4)
Desktop (please complete the following information):
Additional context
swa
.The text was updated successfully, but these errors were encountered: