Quick answer
With Fluid compute, Hobby functions are documented up to 300 seconds. Vercel announced an opt-in 1,800 seconds (30 minutes) beta maximum for Pro and Enterprise Node.js and Python functions.
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Function maximum durationDefault and maximum are both 300 seconds in the documented Fluid compute table. | 300 seconds | Hobby; Node.js/Python with Fluid compute | VercelAug 22, 2026 |
| Function maximum durationBeta above 800 seconds, requires Fluid compute, and requires maxDuration opt-in. | 1,800 seconds (30 minutes) | Pro and Enterprise | VercelAug 22, 2026 |
Why does this limit matter?
A function that never returns or waits too long on an upstream call can terminate with FUNCTION_INVOCATION_TIMEOUT.
The platform maximum does not automatically change an individual route's configured maxDuration.
What should you check?
- Confirm whether Fluid compute is enabled.
- Confirm the runtime and plan.
- Inspect the route-level or project function duration configuration and deployment logs.
How to configure maxDuration
For a Next.js App Router route, Vercel's changelog shows an exported route constant. The configured value must remain within the plan and runtime ceiling.
export const maxDuration = 1800;
export async function POST(request: Request) {
return Response.json({ ok: true });
}The 1,800-second setting is a beta capability for eligible Pro/Enterprise Node.js or Python functions using Fluid compute.
Important caveats
- Durations above the prior 800-second ceiling are beta and limited to the runtimes named in Vercel's announcement.
- Edge runtime streaming behavior is different from Node.js and Python function duration.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related