Isn't the product called "Workflow" ?

Exact same issue here on prod.

@sourfruit it actually is "Vercel Workflow" singular. Thanks for checking!

I removed the other tag

Thanks for sharing an example repo. Starting to dig into this now, but it'll take me some time.

In case it helps before I can get through debugging, I asked v0 for some suggestions. Looks like you may have already tried some of this, but here's what it gave me:

Here are a few things to check:

Route Handler Configuration

Make sure your .well-known/workflow/* routes are properly configured as API routes in your Next.js app. Since you’re using React Router, ensure these handlers are accessible at the correct paths:

1
/api/.well-known/workflow/definition
2
/api/.well-known/workflow/step

Function Configuration

Try adding explicit function configuration to your workflow handlers:

1
export const runtime = 'nodejs'
2
export const dynamic = 'force-dynamic'
3
export const maxDuration = 300 // 5 minutes

Debugging Steps

1. Check your Vercel Function logs in the dashboard to see if the workflow handlers are being invoked
2. Verify the workflow definition is accessible at https://your-domain.vercel.app/.well-known/workflow/definition
3. Test the step handler endpoint directly

Since Workflows is still in beta, there might be some issues that haven’t been worked out yet. I'll make sure your example is shared with the Workflows engineers too

Did you find any workaround?

Hello. I am encountering the exact same issue and have tried everything i can think of. It’s working perfectly locally but I simply am not able to get it working in the Vercel deployment.

@amyegan i tried you solution, defined handlers explicitly, and it works locally but simply does not work when deployed to Vercel. Workflows are stuck in Pending.

Any suggestions?

Thank you,

Julian

I figure out my issue and leaving this message here in case other people get stuck.

Because I implemented authentication and had a middleware/proxy the workflow routes were not accesible so the workflow was starting but was then stuck on pending.

I had the same issue and also figured out that it was missing an exception in the middleware file.

Thanks for coming back to share your solutions