Next.js `basePath`: queue-triggered flow route fails on Vercel with MODULE_NOT_FOUND `.next/server/pages/<basePath>/.well-known/workflow/v1/flow.js`
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- next.js, node.js, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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)?
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.5k
- Forks
- 401
- Merge medio
- 1 d 21 h
- PR fusionados (30 d)
- 201
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de vercel/workflow
-
getPortLazy re-runs OS port discovery on every call when it finds no portPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
node-module-esbuild-plugin: getImportedIdentifier only checks the first named import when locating a violationPosiblemente ocupada @div-cowboy la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel/workflow#5057 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
code-transform.mdx §ID Generation omits the package-shipped `name@version` ID formPosiblemente ocupada @Mohith26 la tomó hace 113 días. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
Todos los issues de vercel/workflow
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 87/100
Los mantenedores suelen responder en 1 día
-
🛠️ dette technique
Dificultad 2/5 1-3 horas Aptitud para principiantes 61/100
betagouv/mon-entreprise#4752 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Los mantenedores suelen responder en 2 días
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día