Vercel Functions using the Node.js and Python runtimes now support execution durations up to 30 minutes for Pro and Enterprise teams, more than 2x the previous 800 second limit. Support for additional runtimes is coming soon.
Use longer-running Functions for work that needs more time to finish, including:
Fluid Compute keeps long-running work cost-efficient. Active CPU billing only applies while your code is executing, and pauses while your Function is waiting on I/O such as AI model calls, database queries, and third-party APIs.
Set
For other runtimes and frameworks, configure
Durations above 800 seconds are in beta and require Fluid Compute. Learn more about configuring max duration for Vercel Functions in the documentation.
Read more
Continue reading...
Use longer-running Functions for work that needs more time to finish, including:
Long LLM reasoning and tool calls
AI responses that stream for several minutes
Document and media processing
OCR and extraction
Web scraping and browser automation
Complex Workflow steps or Queue handlers
Fluid Compute keeps long-running work cost-efficient. Active CPU billing only applies while your code is executing, and pauses while your Function is waiting on I/O such as AI model calls, database queries, and third-party APIs.
Set
maxDuration to opt in. For Next.js App Router, configure it in the route file:For other runtimes and frameworks, configure
maxDuration for a specific function path in vercel.json:Durations above 800 seconds are in beta and require Fluid Compute. Learn more about configuring max duration for Vercel Functions in the documentation.
Read more
Continue reading...