Project: truong-an (team: nguyendotung-2890's projects, Hobby plan)
Stack: Next.js 16.2.9, App Router, ~900+ statically generated pages via generateStaticParams
Symptom: Every vercel --prod --yes deployment (CLI v54.18.7, latest) gets stuck indefinitely showing "Building…" in the terminal. vercel inspect <deployment-url> always returns:
status UNKNOWNBuilds . [0ms]
It never progresses to Ready or Error, even after waiting 15+ minutes. This has been happening consistently for the past several hours across many separate deployment attempts.
What I've already tried (none fixed it):
- Updated Vercel CLI to latest version (54.18.7)
- Removed all previous/stuck deployments before each retry
- Tried both Turbopack (default) and
next build --webpack - Confirmed no
vercel.jsonexists in the project (ruled out legacy builds config) - Confirmed no
middleware.tsfile exists (ruled out the Next.js 16 middleware→proxy rename issue) - Cleared local
.vercel/outputand.nextbuild caches before retrying - Local
npm run build(plainnext build) always succeeds cleanly with zero errors - Local
vercel build --prod --yes(simulating the remote build) intermittently fails withError: Unable to find lambda for route: /bai-viet/<some-slug>— but which specific route fails changes between build attempts, and the site itself builds fine with plainnext build
Ask: Since local troubleshooting is exhausted and this looks like something specific to how the build/deploy pipeline handles this project on Vercel's side, could someone please check the build logs directly for project truong-an under team nguyendotung-2890's projects? Happy to provide any deployment IDs needed.