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

未关闭
#4,971 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
backend, devops

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)?
主要语言
TypeScript
星标
2.5k
派生
401
平均合并
1 天 21 小时
30 天内合并 PR
201

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

vercel/workflow 的其他 Issue

查看 vercel/workflow 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。