Upload Timed Out. Unsure if deployment was successful or not.

[sarveshrekhta]

When trying to build and deploy on azure static web site of nextjs application getting error:

Status: InProgress. Time: 488.4082689(s) Status: InProgress. Time: 503.6600971(s) Status: InProgress. Time: 518.931374(s) Status: InProgress. Time: 534.2865189(s) Status: InProgress. Time: 549.5406369(s) Status: InProgress. Time: 564.8035574(s) Status: InProgress. Time: 580.049225(s) Status: InProgress. Time: 595.9923613(s) Upload Timed Out. Unsure if deployment was successful or not.

PLEASE RESOLVE THIS ISSUE AT EARLIEST. TODAY IS GOING TO LIVE ON PRODUCTION MIDNIGHT.

A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Device info (if applicable):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[dcamposDS]

Same Problem:

Status: InProgress. Time: 470.214519(s) Status: InProgress. Time: 485.3318973(s) Status: InProgress. Time: 500.4088684(s) Status: InProgress. Time: 515.4787595(s) Status: InProgress. Time: 530.5814491(s) Status: InProgress. Time: 545.6464803(s) Status: InProgress. Time: 560.7208778(s) Status: InProgress. Time: 575.8037714(s) Status: InProgress. Time: 590.931524(s) Upload Timed Out. Unsure if deployment was successful or not.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ Exiting

Build Operation ID: 4f446ab6feef72ae OS Type : bullseye Image Type : jamstack

Using Node version: v18.20.4

Using Yarn version: 1.22.15

---End of Oryx build logs--- Web App Runtime Information. OS: linux, node version: 18 Finished building function app with Oryx Zipping Api Artifacts Done Zipping Api Artifacts Zipping App Artifacts Done Zipping App Artifacts Uploading build artifacts. Finished Upload. Polling on deployment.

[wkdcode-dane]

Same problem for me:

Status: InProgress. Time: 474.3635293(s) Status: InProgress. Time: 489.6766763(s) Status: InProgress. Time: 504.9344784(s) Status: InProgress. Time: 520.0434616(s) Status: InProgress. Time: 535.1539244(s) Status: InProgress. Time: 550.25868(s) Status: InProgress. Time: 565.3898529(s) Status: InProgress. Time: 580.502099(s) Status: InProgress. Time: 595.6168328(s) Upload Timed Out. Unsure if deployment was successful or not.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ Exiting

Seems like a persisting issue that's been around for a number of years now, with the only fix being to keep trying to upload until it works, which doesn't quite cut it.

Have there been any explanations behind this at all? Or anything we can do to remedy the problem?

I'm using Next.js my side, seems like the rest of the logs seem okay and the build process is fine, it's just the upload that looks to be failing.

[mt-yusei1109]

Same problem for me

[wkdcode-dane]

Wanted to chime in some more on this problem, I've recently done some tests on my end.

• First I've tried deploying the app later in the evening (11pm) at a quieter time, because reading other issues some seem to have suggested it may make a difference at a point where the server isn't experiencing as much traffic. This did not make a difference in my case, it timed out at around 595 seconds as it always seems to.
• I've tried to deploy another Next.js project I have, it's built in a similar manner to the one I'm having problems with, but the same thing happened, it times out at the 595s mark.
• I tried deploying a completely fresh Next.js application on a fresh slot, this seemed to fly through and work without any problems. I suspect this is because the bundle/file is is relatively small since it's an empty project.

It's seeming like it might be a problem related to the bundle size of the project, which seems silly because my project doesn't contain a crazy amount of NPM packages and all of them are tried and tested.

These are my dependencies:

"dependencies": {
    "@mui/icons-material": "^5.15.20",
    "@mui/material": "^5.15.20",
    "@mui/x-date-pickers": "^7.7.1",
    "@tanstack/react-query": "^5.28.4",
    "moment": "^2.30.1",
    "next": "^14.1.4",
    "next-auth": "^4.24.7",
    "openapi-fetch": "^0.9.3",
    "react": "^18",
    "react-datepicker": "^7.1.0",
    "react-dom": "^18",
    "react-hot-toast": "^2.4.1"
  },
  "devDependencies": {
    "@emotion/react": "^11.11.4",
    "@emotion/styled": "^11.11.5",
    "@tanstack/eslint-plugin-query": "^5.27.7",
    "@tanstack/react-query-devtools": "^5.28.4",
    "@types/node": "^20.14.2",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "autoprefixer": "^10.0.1",
    "eslint": "^8",
    "eslint-config-next": "14.1.3",
    "openapi-typescript": "5.4.0",
    "postcss": "^8",
    "tailwindcss": "^3.3.0",
    "typescript": "^5.4.5"
  },

I don't think these dependencies are really a big ask or out of the ordinary.

To me it seems like the timeout limit is hard locked at like 600 seconds, which seems like an amount that's not fit for purpose for a lot of front end frameworks that widely use the NPM eco-system.

[xrfg]

@wkdcode-dane did you manage to fix it somehow? I am also experiencing this problem...

[elksson]

Also experiencing this issue