I am using NestJS.
All Vercel Workflows calls are stuck in a pending state.
@stanb Can you share some more information about your setup and provide a minimal reproduction example? Feel free to also create a github issue on GitHub - vercel/workflow: Workflow DevKit: Build durable, reliable, and observable apps and AI Agents in TypeScript · GitHub and tag me (@vaguelyserious) on it, so we can automatically cross-link any PRs for fixes we might do
I have a monorepo, nestjs backend is at apps/backend.
I deploy through CI via: vc pull + vc build + vc deploy
Locally, all workflows are running just fine, but on vercel they are just stuck in pending state w/o any error logs.
For local vc build, I inpect .workflow files manually and they seems okay: i.e. paths are correct.
One thing though: because vercel doesn’t pick up root-level .nestjs/workflow files, I have to build them into dist/workflow.
Creating minimal example will take time, but I’m on it.
@stanb Thanks, a minimal repro would allow me to fix this quickly. In the meantime, can you share a few run IDs for runs that are stuck for you?
wrun_01KM5328Y4E5767D97RVD4NW6K
wrun_01KM646VBTADW5Y08FV0EZKSRJ
here is minimal example, same behavior
cutsom script is needed to customize workflow build step
Thank you @stanb . Tracking this in [nest] Fix Vercel build output when using NextLocalBuilder
got it, thank you
i’d rather rewrite to hono/nitro then
please dont support nestjs ever its godless thing