Upload Timed Out. Unsure if deployment was successful or not. #942
Comments
|
##[error]Error: The process '/usr/bin/bash' failed with exit code 1 When executing from Azure DevOps will get this message sporadically. On subsequent retries we will have some success. We are using vmImage: ubuntu-latest to execute |
|
Can you please provide the app details so we can investigate? If you don't feel comfortable sharing them here, feel free to file a support ticket. |
Currently only static content, we have the following files. app.js, config.json, favicon.ico, index.html, readme.md and vancity.css |
|
@mkarmark I am also running into this issue. I have an app that is mostly unchanged from the react template. Deploying the app by itself works fine, but as soon as I add an API (I've tried both C# and typescript function apis), I get the timeout issue. It does seem to actually finish deploying, but it takes another 5 or so minutes for the API to show up in the "apis" section of my static web app in the azure portal. My app can be found here if it helps: https://github.com/ssyrell/purpleair-dashboard Here is a failed deployment: https://github.com/ssyrell/purpleair-dashboard/actions/runs/3221345766 |
|
me too... |
|
Me three. Intermittent timeout failures. Example failure: https://github.com/MaxWilson/POCDungeonDraw/actions/runs/3246742217 Sometimes the live web site gets updated, sometimes it doesn't. I can't detect a pattern except that it several failures in a row are followed by several successes in a row--like it's an environment issue and not an issue linked to my code. Maybe there are certain times of day when load on SWA servers is too heavy? |
|
Same issue here as well, details below, but essentially the upload occasionally times out. Once it does, as mentioned in other reports, it will generally fail a few times and then start succeeding a few times. We have less success in the morning (GMT). DeploymentId: a85c6509-ff2e-4683-81ca-fa3ee09a11e0 App Directory Location: '/build' was found. For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ |
|
We have the same problem, using a azure devops pipeline ( task AzureStaticWebApp@0). |
|
We also have this problem with azure static web app |
|
We also have this problem. |
|
Same issue... any workaround? |
|
Same happening here... Any updates? |
|
same issue as well |
|
Facing the same issue today ... i created a full stack C# with Blazor & Az Fx all .NET7 ... GH action fails with the error - "Upload timed out. unsure if deoloyment was successful or not" ... and i have a demo in 1 hour time :( |
|
Me 4 |
|
I encountered this issue while attempting to follow the Build an Azure Static Web Apps website with Blazor and serverless API tutorial. I tried stepping through this tutorial three times. Each time the Build and Deploy job failed reporting |
|
same issue |
|
This issue is back again. |
|
same issue |
|
Same issue for me. For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ |
|
HI is this resolve?, we keep running the same issue for a couple of times now App Directory Location: 'out' was found. For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ |
|
Same issue here. The "Environments" blade in the Azure portal seems to be stuck in the "Uploading" status:
|
|
same issue, |
|
+1 |
|
+1 Just ran through the quick start and how-to guides in the documentation and received this error. |
|
Got a response from MS from our service request and apparently they found out that the timeout period for the deployment steps is hard coded and if file size is large in combination with some intermittent network issue then you'll encounter this error. The work around that MS suggested to us was either we breakdown our deployments into smaller chunks in the pipeline or deploy in a different time of the day(*When its not very busy which is before lunch time in our timezone) so as a high performing engineer I choose the latter(LOL) .. Its quite annoying cuz this means there is no guarantee that our hotfixes could be deployed in time since there is no guarantee that pipeline wont fail especially in the afternoon |
|
@abdulpapalek do they offer any ETA for the fixing? I can't imagine they hard-code such a critical variable... 🤬 |
|
@zjhch123 not really, i dont think they are fixing it anytime soon which is a bummer because we'll be adding 2 new big packages |
|
Ok I find a solution just add - app_build_timeout_seconds: 1800 on your file yml |
|
@AntoineSmet that is only for the build. Unfortunately there is no easy way around the deployment polling timeout. This is the sample code that MS sent us
|
|
We've just had the same problem on a critical site. Deployment before 0900 before business hours, showing as "Uploading", but never resolving. Multiple deployments not resolving. This is /not/ a large deployment, but "wait until quiet" is not an acceptable solution. |
|
Same issue for me since yesterday... |
|
Yes, I also have the same issue, very frustrating. It was working fine when set up initially in March, but recently have seen this error occur randomly. Is there any workaround or solution? Perhaps a solution/hack is to implement a retry with e.g. https://github.com/Wandalen/wretry.action |
|
@roldengarm So for me at least it is working again. It seems to be a temporary, yet reoccuring problem... |
|
I also had this issue a few days back for the first time, during my holidays, and redeploying now worked! A bit frustrating, especially considering the workaround given by MS |
Yes, it is always working the second time, but it is very annoying as I have to re-run our pipeline manually. |
|
Same issue here. Is there any update on this? |
|
Having the same issue here. And the environment has been stuck at |
|
same issue |
|
Same issue |
|
Same issue here. Start time of the event appears to be timed with a significant outage of the GitHub Actions/Runner workload which has subsequently been resolved a couple hours back. |
|
Same issue from today, it happens only in Production. Staging deployments are OK. |
Yes but runners are working fine now. but still showing the same error |
|
created a new issue #1396 |
|
same here |
|
Re-run the same job in a different time. It might help. |
|
I get this error in Azure Devops after 600 seconds. Is there a resolution already? |
|
I'm seeing this with the Github Actions Deploy in a staging build for a PR. |
|
@elad320011 @Cypher1 are you deploying Next.js workloads? If so, can you share the region of your static web apps and its default hostname/url in the thread #1427? |
|
No, Vue static site and Node Azure Functions
…On Tue, 12 Mar 2024, 2:41 am Thomas Gauvin, ***@***.***> wrote:
@elad320011 <https://github.com/elad320011> @Cypher1
<https://github.com/Cypher1> are you deploying Next.js workloads? If so,
can you share the region of your static web apps and its default
hostname/url in the thread #1427
<#1427>?
—
Reply to this email directly, view it on GitHub
<#942 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIRUHX6CJD5F6IG6HRJHLLYXXNDTAVCNFSM6AAAAAAQ63LORGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYG42DONBYHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
and others
No description provided.
The text was updated successfully, but these errors were encountered: