Next.js `basePath`: queue-triggered flow route fails on Vercel with MODULE_NOT_FOUND `.next/server/pages/<basePath>/.well-known/workflow/v1/flow.js`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- next.js, node.js, typescript
Research direction
Start by tracing how the Vercel build output and route table handle the workflow flow route when basePath is set; the issue names .next/server/app/.well-known/workflow/v1/flow/route.js, routes-manifest.json, and app-path-routes-manifest.json. Compare those entries with the failing launcher lookup under pages/admin/.well-known/workflow/v1/flow.js and the behavior without basePath. Done means queue deliveries reach the App Router handler on Vercel with basePath enabled.
Written by the indexing model from the issue text.
Description
Summary
A Next.js app with basePath: "/admin" deploys to Vercel. Every queue delivery to the flow route fails before any user code runs, so no workflow run ever leaves queued. Runs started with start() are accepted, then retried every ~5 s forever.
This looks like the follow-up named in #2732: "the generated Vercel/Next output serves internal workflow invocation at /v2/.well-known/workflow/v1/flow, but [...] appears to be a Vercel/Next build-output route-table issue". #1864 reported the same error and was closed by #2732, but the platform part still reproduces on current versions. #3483 (also basePath: '/v2') may be the same defect seen from the queue side.
Versions
next16.2.6 (App Router, Turbopack build)workflow5.2.2,@workflow/next5.0.5,@workflow/core5.2.2,@workflow/world-vercel5.2.2,@vercel/queue0.8.0- pnpm monorepo, app at
apps/admin(launcher runs from/var/task/apps/admin) - Fluid compute, Node.js runtime, Pro team
Configuration
next.config.ts (simplified):
export default withWorkflow({
basePath: "/admin",
// ...
})
proxy.ts excludes the workflow routes, as the docs ask:
matcher: ["/", "/((?!\\.well-known/workflow/|_next/static|_next/image|favicon.ico).*)"]
What happens
The queue (User-Agent: vercel-queue/v2beta) sends POST /admin/.well-known/workflow/v1/flow. The function fails in ~8–23 ms with FUNCTION_INVOCATION_FAILED:
Failed to handle /admin/.well-known/workflow/v1/flow Error: Cannot find module './.next/server/pages/admin/.well-known/workflow/v1/flow.js'
Require stack:
- /var/task/apps/admin/___next_launcher.cjs
- /opt/rust/nodejs.js
code: 'MODULE_NOT_FOUND'
- Observability lists the route as
/admin/.well-known/workflow/v1/flow(with the base path). Every other route in the same deployment is listed without it, e.g./assistant. - The launcher looks under
pages/and includes the base path segment. - The build emits the handler as an App Router route:
.next/server/app/.well-known/workflow/v1/flow/route.js.routes-manifest.jsonandapp-path-routes-manifest.jsonlist/.well-known/workflow/v1/flow. app/.well-known/workflow/v1/config.jsonholds thequeue/v2betatrigger for topic__wkf_workflow_*.
Expected
The queue trigger invokes the App Router handler at app/.well-known/workflow/v1/flow/route.js, as it does for an app without basePath.
Evidence
- Deployment:
dpl_CaToLKmeYmbxizgPPnDbv9guLFsL(production, branchmain) - Workflow run:
wrun_41M5EFC5JP90T9NVPKN8WSWW0X - Request ID:
zjnrt-1792562314900-3ec8808307b5(2026-10-21 05:58:34 UTC,sin1)
Questions
- Is there a supported way to run Workflow on Vercel with a Next.js
basePathtoday? - If not, is there a workaround that keeps
basePath(the app is a Multi-Zones zone mounted at/admin)?
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 401
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 201
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/workflow
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
node-module-esbuild-plugin: getImportedIdentifier only checks the first named import when locating a violationPossibly taken @div-cowboy claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel/workflow#5057 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
code-transform.mdx §ID Generation omits the package-shipped `name@version` ID formPossibly taken @Mohith26 claimed this 113 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
Similar issues
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
device-management-toolkit/sample-web-ui#3711 ·
Maintainers usually reply within 1 day
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPossibly taken @seenimohamed claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ardia-browser/ardia#2769 ·
Maintainers usually reply within 1 day