No I haven’t been able to fix this yet. I had raised it to the vercel team and below was the reply that I got. I am still in discussion with them around this.
The function times out after 340 seconds and not 800 seconds. My current workload is I need to process a bulk job which can take around 2-3 hours to be completed. In order to process it through my nextJS API’s I divided this workflow in chunks where each chunk can take around 2-10 minutes.
Below is the reply from Vercel team. They need some more data from my end to verify this.
The critical distinction here is that the timeout you are experiencing is happening on the response side of the connection. While packets from Inngest to Vercel keep the initial request alive, the connection is considered idle if your Vercel Function does not send any data back to Inngest. Our infrastructure provider terminates any connection that does not send or receive data for more than 340 seconds (5.7 minutes). If your function is processing a task and does not begin to stream a response back to Inngest within that timeframe, the connection is flagged as idle and closed. This aligns perfectly with the failure timing you've observed. The key is that the response stream from your Vercel Function must remain active.
