504: GATEWAY_TIMEOUT out of nowhere
Unanswered
Kangal Shepherd Dog posted this in #help-forum
Kangal Shepherd DogOP
Hi there,
since last week we are dealing with the described error.
It says "This Serverless Function has timed out.". First of all, this error came literally over night without any new deployments etc. and we noticed if by luck the next day, it was working the evening before fine. All deployment checks passed as usual. In the logs, there is nothing that can point us in any direction.
Searching online, we found a few solutions. We changed the function region to the nearest server location, but this did not work.
We have updated the route.ts files maxDuration to 300 seconds, as our Pro plan gives us that time, but also no success here.
We moved one smaller project where this also occured to the pages directory structure and the issue was gone.
So, before changing to pages directory in this bigger project we are working on now, are there any further suggestions on how to tackle this? Or is this a bug we should report to Vercel directly?
Further info about the stack:
Next.js Version 14.0.1
Headless WordPress and WooCommerce hosted on our own servers
since last week we are dealing with the described error.
It says "This Serverless Function has timed out.". First of all, this error came literally over night without any new deployments etc. and we noticed if by luck the next day, it was working the evening before fine. All deployment checks passed as usual. In the logs, there is nothing that can point us in any direction.
Searching online, we found a few solutions. We changed the function region to the nearest server location, but this did not work.
We have updated the route.ts files maxDuration to 300 seconds, as our Pro plan gives us that time, but also no success here.
We moved one smaller project where this also occured to the pages directory structure and the issue was gone.
So, before changing to pages directory in this bigger project we are working on now, are there any further suggestions on how to tackle this? Or is this a bug we should report to Vercel directly?
Further info about the stack:
Next.js Version 14.0.1
Headless WordPress and WooCommerce hosted on our own servers