10s Timeout when using NextJS server routes

Admin
1

Hello,

My Netlify site name is: d91183aa-4435-4f5e-869f-5ad8be273cbb

I’m experiencing the same issue as the user mentioned above, where the lambda function is timing out after 10 seconds. This timeout is significantly impacting our users.

Could you please increase the timeout to 26 seconds for our site as well? The error message and details are similar to the example provided by the other user:

errorMessage: “Task timed out after 10.02 seconds”
errorType: “LambdaTimeout”

Thank you for your assistance in resolving this issue.

Best regards,

2

Hi @alan_gama,

Thanks for reaching out and welcome to Netlify’s Support Forums!

I’ve increased the function time limit to 26 seconds for the site. You’ll need to re-deploy the site for this increase to take effect.

1 Like
3

Hi @Melvin , I get the same issues.

Could you please increase the timeout to 26 seconds for our site as well?

Site ID : eb36bfbb-73e8-4056-8344-0aee7fd04a4a

LambdaTimeout - 2024-04-26T06:01:59.665Z 3d80fc2a-27c3-4059-b0d1-7766d650d48f Task timed out after 10.02 seconds

Thanks

4

Hi @tichaws,

Thanks for reaching out! I increased the function timeout limit to 26 seconds. You’ll need to re-deploy the site for the change to take effect.

5

Hi @Melvin I got the same issue but im on an open source plan would it be possible to increase the timeout limit?

6

Hi @BritneyPaul,

Thanks for reaching out! Could you let us know the site name of the site that you would like the function timeout increased on? If you could provide the sitename such as sitename.netlify.app.

7

Yes sorry @Melvin the Site ID is: 6e4ebdb0-c62f-45e2-acc1-c2d70d50fc08

Could you please increase the timeout to 26 seconds?

Thanks

8

Hi @BritneyPaul,

Thanks for following up. I’ve increased the function time limit to 26 seconds for that site. Please re-deploy the site for the change to take effect.

9

I am facing the same issue. My site is clonestoxx.instantmarket.ing. Could you please increase timeout to 150 seconds?

10

@abhimanyutokas Netlify will respond, but I believe the maximum execution limit is 26 seconds, as mentioned in the Custom deployment options for functions in the documentation:

Maximum execution limit can be increased by contacting support.
Synchronous functions can have a maximum execution limit of 26 seconds.

For longer executions you would need to use something else, perhaps Background Functions.

11

Hi there! we can definitely bump you up to 26 seconds, but you’ll need to be on the Pro tier for us to make that change - that’s a requirement that applies to everyone who wants a bigger timeout. You can upgrade to Pro easily through the Netlify UI dashboard. Please note the max function timeout is 26s set by AWS lambda.

If you let us know when you have upgraded, we can change the settings for you!

12

I have an api that is hit on user interaction which takes about 2 min to resolve.

13

Our max is 26s. If you need more time I’d encourage you to use edge functions. I’m attaching a resource for you to use below.

14

Hello, could you also bump my timeout to 26s please?

00e9df60-badf-494e-8442-2d81504cec5d

15

Hi :wave:t6:
Good news! we’re now letting Netlify Functions run for up to 30 seconds, for everyone. :partying_face:

This has been a highly requested feature, especially since AI entered the scene so strongly. So now you can e.g. have your LLM stream back responses to the client via a serverless function, without worrying about going over the previous 10-second default.

It also means that if some of your server-rendered pages or API endpoints take a bit longer than the usual due to issues outside your control (say, a third-party API being slow), you’d experience less timeouts.

Have fun developing!

1 Like