#nextjs

Fred I could not confirm a per deployment function limit in the current docs, so I would measure the real output instead of predicting it. Run vercel build locally with the same Next.js version and count the folders ending in .func under .vercel/output/functions. That is what gets uploaded. If the count is higher than you expect, the heavy POST route at about 319 MB is a likely culprit because it gets its own function and can pull other routes with it. Trim its trace with outputFileTracingExcludes for the packages it never loads at runtime (big dev or build only dependencies, platform binaries for

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting