Vercel more than doubles Workflow step runtime

Vercel raised the ceiling on Workflow step runtime from roughly 800 seconds to 1,800, per its changelog. It's a beta feature, gated behind an environment variable called VERCEL_ENABLE_WORKFLOW_EXTENDED_MAX_DURATION=1, and it needs a redeploy plus Fluid compute and a compatible Node.js or Python runtime to take effect. Hobby projects don't get it. They stay capped at 300 seconds.

This matters most if you've built anything with a long-running agent step, a batch job, or a multi-stage generation task that used to blow past 13 minutes. The old limit forced a specific pattern: break the work into chunks, checkpoint state somewhere, and resume on the next invocation. That's real code, real state management, and real edge cases around partial failures.

With a 30-minute ceiling, a lot of that scaffolding becomes unnecessary. If your longest step ran 14 to 25 minutes, you can likely collapse it back into one function call and delete the resume logic entirely.

The catch is the runtime requirement. This isn't a flip-a-switch change on every project. You need Fluid compute enabled and a Node.js or Python runtime that supports the extended duration, so teams on older runtime pins or non-Fluid deployments don't get the benefit until they migrate. The changelog doesn't say when this graduates out of beta or whether 1,800 seconds is a hard ceiling or a placeholder.

Worth watching: whether Vercel treats this as a stepping stone toward removing step-duration limits entirely, or whether 30 minutes is where they intend to stop. For anyone running agent pipelines with genuinely open-ended steps, that distinction decides whether you drop the resume mechanism entirely or only loosen its trigger threshold.