Skip to content

Commit 8e3e4ad

Browse files
authored
docs: update maxDuration info (#60086)
1 parent 7cbcea3 commit 8e3e4ad

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

docs/02-app/02-api-reference/02-file-conventions/route-segment-config.mdx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -200,8 +200,10 @@ Support for `preferredRegion`, and regions supported, is dependent on your deplo
200200
201201
### `maxDuration`
202202

203-
Based on your deployment platform, you may be able to use a higher default execution time for your function.
204-
This setting allows you to opt into a higher execution time within your plans limit.
203+
By default, Next.js does not limit the execution of server-side logic (rendering a page or handling an API).
204+
Deployment platforms can use `maxDuration` from the Next.js build output to add specific execution limits.
205+
For example, on [Vercel](https://vercel.com/docs/functions/serverless-functions/runtimes#max-duration).
206+
205207
**Note**: This settings requires Next.js `13.4.10` or higher.
206208

207209
```tsx filename="layout.tsx | page.tsx | route.ts" switcher
@@ -212,10 +214,6 @@ export const maxDuration = 5
212214
export const maxDuration = 5
213215
```
214216

215-
> **Good to know**:
216-
>
217-
> - If a `maxDuration` is not specified, the default value is dependent on your deployment platform and plan.
218-
219217
### `generateStaticParams`
220218

221219
The `generateStaticParams` function can be used in combination with [dynamic route segments](/docs/app/building-your-application/routing/dynamic-routes) to define the list of route segment parameters that will be statically generated at build time instead of on-demand at request time.

0 commit comments

Comments
 (0)