Next.js `basePath`: queue-triggered flow route fails on Vercel with MODULE_NOT_FOUND `.next/server/pages/<basePath>/.well-known/workflow/v1/flow.js`

Abierto
#4,971 1 comentario 0 reacciones 0 asignados Ver en GitHub

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
Área
backend, devops

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

  • next 16.2.6 (App Router, Turbopack build)
  • workflow 5.2.2, @workflow/next 5.0.5, @workflow/core 5.2.2, @workflow/world-vercel 5.2.2, @vercel/queue 0.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.json and app-path-routes-manifest.json list /.well-known/workflow/v1/flow.
  • app/.well-known/workflow/v1/config.json holds the queue/v2beta trigger 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, branch main)
  • Workflow run: wrun_41M5EFC5JP90T9NVPKN8WSWW0X
  • Request ID: zjnrt-1792562314900-3ec8808307b5 (2026-10-21 05:58:34 UTC, sin1)

Questions

  1. Is there a supported way to run Workflow on Vercel with a Next.js basePath today?
  2. 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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de vercel/workflow

Todos los issues de vercel/workflow

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.