Sudden Build Failures and Unsuccessful Re-deployments After Vercel CLI Update (34.1.7) #6714
Replies: 4 comments 10 replies
-
Same issue here. Current vercel CLI version is 34.1.7 according to the build logs. Yet in the past this kind of forced downgrade worked and helped me avoid a bug of the latest vercel CLI, but not this time. I tried: The build logs show that the version I want is well taken into account and installed prior to the build itself, but in the end it still displays the same strange "/var/task/sandbox" error block, and the deployed NodeJS app does not get started. |
Beta Was this translation helpful? Give feedback.
-
I'm facing the same issue. The build fails before it even starts. Did you find any fixes? @CamaradePopoff @lgauthier1 is the only solution to wait it out until Vercel fixes it from their side? |
Beta Was this translation helpful? Give feedback.
-
We are facing a similar problem... Build Completed in /vercel/output [1m]
--
14:16:26.412 | Deploying outputs...
14:16:26.461 | at qze (/var/task/sandbox.js:405:12920)
14:16:26.462 | at w8r (/var/task/sandbox.js:407:33497)
14:16:26.462 | at async Mze (/var/task/sandbox.js:407:33236)
14:16:26.462 | at async P8r (/var/task/sandbox.js:409:4108)
14:16:26.462 | at async Qze (/var/task/sandbox.js:409:4952)
14:16:26.462 | at async N8r (/var/task/sandbox.js:409:1388)
14:16:26.462 | at async Promise.all (index 172)
14:16:26.462 | at async D8r (/var/task/sandbox.js:409:479)
14:16:26.462 | at async zze (/var/task/sandbox.js:407:36120)
14:16:26.462 | at async f_r (/var/task/sandbox.js:425:2334) {
14:16:26.462 | idx: 2511
14:16:26.462 | }
~~~~
An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help
Redeployment of a previously successful deployment fails. We are currently contacting the Vercel development team to see if they can help. If we make any progress, I will share it. If anyone has any solutions, please let me know🙏 |
Beta Was this translation helpful? Give feedback.
-
After analysis, we have confirmed that the error is present. However, it does not prevent the build from completing and does not affect the functionality of our API. This log has been observed in multiple projects and does not seem to cause any blockage. Therefore, I am closing this discussion. It would be great if we could get some answers from the Vercel team regarding the root cause of this issue. |
Beta Was this translation helpful? Give feedback.
-
Page to Investigate
NA
Steps to Reproduce
Hello,
I'm encountering a sudden issue where my project no longer builds successfully, despite there being no changes to the code or dependencies. I've confirmed that dependencies are consistent using npm ci, which indicates that no unexpected changes have occurred. The issue coincided with an update to the Vercel CLI, which seems to be the only significant change.
Error Details:
Moreover, when I attempt to re-deploy older builds that were previously successful and fully operational, they now fail, indicating that the issue may stem from a change at Vercel's end rather than any alterations in my project's setup.
It is puzzling that the build process ultimately reports as successful ("Build Completed") despite the errors listed. I am looking for insights or suggestions on how to resolve these errors or any further diagnostic steps I should take. Any help would be greatly appreciated!
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions