[Bug] Not able to deploy on Vercel after deleting workflow

[raviranjan31]

The Vercel build is still trying to resolve a workflow file that has been deleted from the codebase.

Locally, I saw the same error, but deleting the .next folder resolved it. On Vercel there doesn’t appear to be a way to clear the equivalent build cache, so the issue persists across deployments.

Error log from Vercel:

text

▲ Next.js 16.1.1 (Turbopack)
- Experiments (use with caution):
  ⨯ turbopackScopeHoisting
  Creating an optimized production build ...
✘ [ERROR] Could not resolve "./src/workflows/create-requisition-share-link/definition.ts"
    virtual-entry.js:10:7:
      10 │ import './src/workflows/create-requisition-share-link/definition.ts';

Could you investigate why this stale workflow reference is still being picked up during the Vercel build, and whether there’s a way to force a clean build (similar to deleting .next locally)?

[mburumaxwell]

Having a similar issue. All I did was update workflow from 4.0.1-beta.33 to 4.0.1-beta.37 without changing the source code and vercel could no longer complete build. Rolling back to 4.0.1-beta.33 resolved it. I noticed that experimental.turbopackScopeHoisting is being disabled by workflow since #640. Perhaps this is the issue causing the vercel build to fail/timeout.

[Kinshuk2003]

Hii I would like to work on this issue @TooTallNate @VaguelySerious

[VaguelySerious]

Potentially solved in #700. We might be releasing this soon, and in the meantime, you could try installing the preview package like so:

  // ... rest of package.json
  "dependencies": {
     "workflow": "https://workflow-docs-git-ijjk-validate-cache-and-lower-latency.vercel.sh/workflow.tgz"
     // ... rest of dependencies
  }

[VaguelySerious]

The above PR was released as workflow@4.0.1-beta.39, please see if it resolves the issue for you

[m41denx]

4.0.1-beta.39 still produces Timeout waiting for build-complete message (60 seconds elapsed) on Vercel

[graham-fleming]

although not original post, for Nextjs 16+ default bundler is turbopack which causes freeze for build.

for me adding a --webpack flag in package.json allows build to pass.

"scripts": {
  "dev": "next dev",
  "build": "next build --webpack",
  "start": "next start",
}

[mburumaxwell]

Thanks @ijjk for reverting the change in #712 although now with 4.0.1-beta.40, there's an issue with tsconfig paths which I suspect came in through #705. The error occurs when a workflow file references nothing like @/lib/utils. This time it fails to complete build locally and hangs on GitHub Actions or Vercel build.

[TooTallNate]

@mburumaxwell Could you please provide a reproduction of what you're describing?

[mburumaxwell]

I am only seeing it when using prisma in a moderately sized project when using prisma 6.
mburumaxwell/dependabot-azure-devops#2376
Everything works if workflow is not updated to beta40. I cannot reproduce this on a single app repo so perhaps it has something to do with using a mono repo looking at how long the require path is. I am doubting the "require is not supported" because that would have shown elsewhere.

Update 40min later, I can produce this on the smaller repository now (non monorepo, private). Observation is that the generated app/.well-known/workflow/v1/step/route.js did not do much compiling instead just imported .ts files as used the workflow files but now it does compile.