Quick answer
With Fluid compute, Hobby functions run for at most 300 seconds. Pro and Enterprise functions default to 300 seconds, can be configured up to 800 seconds (generally available), and eligible Node.js, Bun and Python functions can opt in to a 1,800 seconds (30 minutes) extended maximum that is still in beta.
Verified Sep 17, 2026Official source
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 | VercelSep 17, 2026 |
| Function maximum durationGenerally available maximum; the default stays 300 seconds and maxDuration must be raised per function. | 800 seconds | Pro and Enterprise | VercelSep 17, 2026 |
| Function extended maximum duration (Beta)Beta; values above 800 seconds need function-level configuration and are not supported with Secure Compute or Static IPs during the beta. | 1,800 seconds (30 minutes) | Pro and Enterprise | VercelSep 17, 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 800 seconds are beta, need function-level configuration, and are limited to the runtime versions Vercel lists; Secure Compute and Static IPs do not support them during the beta.
- 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