Vercel Functions Max Duration Increased Up to 30 Minutes
Vercel has announced an increase in the maximum execution limit for Vercel Functions, which can now run for up to 30 minutes. This update introduces changes to existing runtime specifications, allowing workflows that previously hit execution timeouts to complete successfully on the platform. Security parameters, resource utilization limits, and dependency updates should be thoroughly reviewed prior to adopting these longer execution windows.
Related tools
Recommended tools for this topic
These picks prioritize high-intent tools relevant to this topic. Some links may include partner or affiliate tracking.
A strong security and edge platform match across CDN, Zero Trust, and app protection.
View CloudflareA high-relevance security pick for identity, secret management, and team access control.
View 1PasswordStrong for identity, OIDC, and B2B auth readers evaluating implementation tradeoffs.
View Auth0Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Maximum Timeout Limit | Typically limited to 10-60 seconds depending on plan | Up to 30 minutes for compatible plans and configurations |
| Execution Use Cases | Short HTTP request-response cycles only | Long-running background tasks, data processing, and complex migrations |
| Timeout Configuration | Strict low limits enforced by platform defaults | Configurable maxDuration setting within project or function configurations |
Action Checklist
- Verify subscription plan compatibility with the new 30-minute execution limit Maximum timeout limits can vary based on your Vercel plan type.
- Update the maxDuration property in your project configuration file Ensure your vercel.json or route-specific configurations explicitly declare the extended duration.
- Review security permissions and gateway timeout settings Long-running functions may require adjusted IAM roles or API gateway configurations.
- Test long-running functions in a staging environment before production deployment Monitor staging resource usage and memory limits under extended runtime conditions.
Source: Vercel Changelog
This page summarizes the original source. Check the source for full details.
