deployment failed - cannot find deployment logs
Hi,
I have a Pages site that is failing to deploy. The Cloudflare dashboard shows there was a deployment error. Where are the deployment logs found? I've looked all over but have had no luck.
Deployment ID is
67a1e1d0-6284-4205-8176-3b924feec893.
Thanks
18 Replies
Check the github workflows section on your github repo
also you shouldnt have to make any github workflow configurations, pages should handle all of that automatically
Thanks for the help X.
Check the github workflows section on your github repoThe github workflow shows the deployment as successful.
Interesting. Normally you can click on "view details" to see build logs.
My assumption is that because you have the github actions yaml file it instead uses github logs
Are you using any perticular javascript framework for your project?
My assumption is that because you have the github actions yaml file it instead uses github logsFrom what I understand, I think that is correct, but I like using Github actions for deployment.
Are you using any perticular javascript framework for your project?I'm using Vite and Remix. The project builds, deploys and runs fine with earlier commits. The deployment is failing after adding a new dependency to the project. I'm looking for the logs so I can debug why this particular dependency is causing the deployment to fail.
Not sure why actions does not log the errors. What I would suggest, if you dont mind, is re-configuring your project to just use cloudflare instead of github actions for deployment. I'm pretty sure just having your repo attached and setting up build configurations should work. Also make sure to delete the .github folder (including the workflows config inside). And set the framework preset to remix if you havent.
Or you could make a new pages project to not have to mess with the current one, and try strictly cloudflare for deployment
You'd only get that if you setup the project through the Git Integration, and are using Pages CI/CD
If you set the project up as Direct Upload/not through Git, you'd need to recreate it entirely to use Git.
You can, however, direct upload via wrangler to a git-based project
I guess the easiest thing to do is making a new project and setting it up with the git integration then
It's a known issue that Direct Upload/pages-action, on issues with functions, will say it suceeded from wrangler and shows as failed in dashboard. Only CF Employees can grab the logs for you, if needed. Does it run locally? Is the function over 1 MiB (if on free)?
Alternatively setting it up with the git integration would expose the error
Can you test locally/repro the issue, and check size?The project builds and runs fine locally. How would I go about checking the size?
It's a known issue that Direct Upload/pages-action, on issues with functions, will say it suceeded from wrangler and shows as failed in dashboard. Only CF Employees can grab the logs for you, if needed.OK, cool, thanks for the confirmation. Thanks for the help X and Chaika 🙏 If any CF employees happen to see this, would it be possible to find out the failure reason for deployment
67a1e1d0-6284-4205-8176-3b924feec893 please?How would I go about checking the size?Depends on the framework. What dependency did you add? Could be a missing dependency (i.e its relying on something node has, for example) or startup cpu time limit Can just escalate if we can't figure it out
What dependency did you add?The dependency causing the failure may be
@react-email/components
https://github.com/resend/react-email
Depends on the framework.The framework is Remix (using Vite). The on disk size of the build directory is 475KB.
Could be a missing dependency (i.e its relying on something node has, for example) or startup cpu time limitOk, that's a couple of options.
Similar issue with react email: https://discord.com/channels/595317990191398933/1219316975180710031/1219703208381775993
The tailwind imports that it uses is very large in size.
Removing react email would most likely fix the issue
well you don't need to remove it is my understanding, just get specifically what you need
https://discord.com/channels/595317990191398933/1219316975180710031/1219707159500296395
but yea, he had the exact same issue with build failing due to startup timeout, because grabbing the entire lib is too big
Oh right, didnt read that far. I though the react email library itself was using a massive import 😅
Thanks for the link to the other thread. The fix described there (removing the
@react-email/components dependency) resolved my deployment issue as well. 🙂