-
SummaryHey Vercel team, Recently, I'm not sure what happened. I haven't made any changes to the dependencies. I'm having trouble with a new deployment in my project - it's giving me a 504 timeout error, and all my previous deployments are showing the same issue. I had a similar problem before and fixed it by changing Could you help me take a look and see what's going on? The final Deployment: 504: GATEWAY_TIMEOUT
Additional information504: GATEWAY_TIMEOUT
Code: FUNCTION_INVOCATION_TIMEOUT
ID: hnd1::fs8k9-1679151302268-044a719e1f27Example |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Thank you for reaching out. The most common reason for a FUNCTION_INVOCATION_TIMEOUT Error is that a Serverless Function reached the timeout limit (10 seconds for Hobby accounts, 60 seconds for Pro accounts, and 90 seconds for Enterprise accounts) because of an upstream provider taking too long to respond. The first step I would typically recommend is to check your upstream provider for slowness. If you already confirmed that isn't the problem, do you have a minimal reproducible example that we can use for debugging? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing these examples. I tried to reproduce the issue in my test app with Next 13.3.0, as specified in your project, and the example functions you provided. But both are working as expected for me. 😕 Since it seems to be caused by some other interaction in the code and configuration options, please share a minimal reproducible example without Firebase or other required keys needed. That will give us a better view of the problem 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Hey @amyegan — thanks for getting back to me so quickly! I did indeed remove Firebase on my Could it be that my serverless function is deployed on a Vercel server that's hanging? Is it possible to re-deploy my function to a different server or something? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
It was the When I run a preview deployment of this code and test the serverless function, it takes over 14 seconds which exceeds the Hobby plan function timeout limit. I went into You should take a look at the various provider wrappers included in |
Beta Was this translation helpful? Give feedback.
-
|
@amyegan Thank you so much! I didn't realize stuff happening in the other pages could affect the serverless functions. This is a huge help 🙏🏻 |
Beta Was this translation helpful? Give feedback.
-
|
@amyegan I just got the serverless function to work by removing all providers/etc. from my One question: does this mean that the function for generating the Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Experiencing something similar, been tinkering a lot and still can't get it working. https://github.com/orgs/vercel/discussions/1910 |
Beta Was this translation helpful? Give feedback.
Thank you for reaching out. The most common reason for a FUNCTION_INVOCATION_TIMEOUT Error is that a Serverless Function reached the timeout limit (10 seconds for Hobby accounts, 60 seconds for Pro accounts, and 90 seconds for Enterprise accounts) because of an upstream provider taking too long to respond.
The first step I would typically recommend is to check your upstream provider for slowness. If you already confirmed that isn't the problem, do you have a minimal reproducible example that we can use for debugging?