Hi Vercel team,
I’m looking for help with a repeatable Preview deployment failure that occurs after the Next.js application build has completed successfully.
Project: okc-wholesale-ai-system
Vercel Project ID: prj_3ziP3WSM9DQUHVDnIZukaHGaq2oV
Current Git Preview deployment: dpl_4D7cfqV3ybMUFAMkgVRdef5YETYg
Earlier deployment showing the same failure: dpl_78Cw4gpv4XRQgnSxmh2XbsVFU96i
Current commit: fc3b7aa6b9bb634bfbd58cef973ca97ae328b976
The deployments successfully complete:
- application compilation
- TypeScript
- static generation
- Next.js Build Output generation
The final visible log is:
Build Completed in /vercel/output
followed by:
Deploying outputs...
The deployment then fails with:
ERR_INVALID_ARG_VALUE errorStep=direct:build
We have already investigated the repository side.
Current verification:
- local Vercel-mode Webpack build passes
- TypeScript passes
- ESLint passes
- safety suite passes 428/428
- git diff --check passes
- secret scan passes
- clean worktree
- no migrations involved
- no provider calls
- no Production changes
We also corrected two repository issues during isolation:
- Vercel builds were switched from Turbopack to Webpack to avoid whole-project Prisma tracing.
- Invalid test-only exports were removed from Next.js route handlers and moved into a library dependency module.
Those fixes passed locally, but the same ERR_INVALID_ARG_VALUE still occurs after Build Output generation on Vercel.
The Vercel Support Agent reviewed the issue and said the specific argument/path/value rejected at direct:build is not exposed in public logs and requires access to internal platform logs.
Could a Vercel team member please inspect these deployment IDs and identify:
- The exact argument, path, or value causing ERR_INVALID_ARG_VALUE.
- Which /vercel/output artifact is being processed when it fails.
- Whether this is a known Next.js / Build Output API / deployment packaging issue.
- Whether there is a project-level configuration issue.
- Whether a cache reset, builder/framework configuration change, or other platform-side remediation is recommended.
We are intentionally avoiding additional speculative deployments or configuration changes until we know what Vercel is rejecting.
No credentials or secrets are included in this post.
Thank you.