All deployments fail out of nowhere
Unanswered
Pyr0Lover posted this in #help-forum
I thought it was a code change which made it so every deployment was giving me a pre-render error.
But I tried to redeploy any of the previous successful deployments, and they also fail.
How is it possible that the code of a successful deployment is not working now?
But I tried to redeploy any of the previous successful deployments, and they also fail.
How is it possible that the code of a successful deployment is not working now?
6 Replies
What is the error?
You can see that there are 2 errors, first something related to no-store, although I dont think thats a problem. And then the pre-render error with static pages.
But you can see that it still manages to generate 2k pages successfully, so Im not sure why it says error fetching data inside one of those pages...
And also, this completes locally, only on vercel does it give error
But you can see that it still manages to generate 2k pages successfully, so Im not sure why it says error fetching data inside one of those pages...
And also, this completes locally, only on vercel does it give error
the error you are getting is explained here
https://nextjs.org/docs/messages/dynamic-server-error
can you share a code snippet of how you are making the fetch?
maybe adding export const dynamic = "force-dynamic"; at the top of the page helps
https://nextjs.org/docs/messages/dynamic-server-error
can you share a code snippet of how you are making the fetch?
maybe adding export const dynamic = "force-dynamic"; at the top of the page helps
I dont see how that can help. Specially since I did not change any logic at all to data fetching, I have tried reverting the code manually to the last succesfull deployment, and it didnt work. I also tried to re-deploy directly from vercel and it also didnt work.
I really struggle to understand how the same code base now gives an error deploying. It makes me think the "vercel build" command got changed. Because the "next build" is still working locally.
I really struggle to understand how the same code base now gives an error deploying. It makes me think the "vercel build" command got changed. Because the "next build" is still working locally.
Lol, it was pre-render error because out of the 2k pages, 1 was giving Internal Server Error, thus the failed to fetch data.
The logs made me think every page was giving error. But anyways, its an API issu not related to nextjs or vercel
The logs made me think every page was giving error. But anyways, its an API issu not related to nextjs or vercel