# New execution duration limit for Edge Functions

**Published:** February 6, 2025 | **Authors:** Shohei Maeda, Kiko Beats

---

> **Note:** This changelog entry is historical. Edge Functions are deprecated for new projects. Use [Vercel Functions](https://vercel.com/docs/functions) with the Node.js runtime and [Fluid compute](https://vercel.com/docs/fluid-compute). Use [Routing Middleware](https://vercel.com/docs/routing-middleware) for request-time routing before a response completes.

Starting on March 1st, 2025, we will begin the rollout of a new execution duration limit of 300 seconds for [Vercel Functions ](https://vercel.com/docs/functions/runtimes/edge)using the Edge runtime.

Previously, functions using the Edge Runtime had no fixed timeout for streaming responses, leading to unpredictable behavior based on system resources and traffic. With this update, functions using the Edge Runtime will consistently allow streaming responses for up to 300 seconds, including post-response tasks like `waitUntil()`.

> **Note:** Please note that Edge Functions must begin sending a response within **25 seconds** to maintain streaming capabilities beyond this period. This limit remains as before.

Learn more about [Vercel Functions using the Edge runtime](https://vercel.com/docs/functions/runtimes/edge/edge-functions).

---

📚 **More updates:** [View all changelog entries](/changelog/sitemap.md) | [Blog](/blog/sitemap.md)