Alabtsamhsfyr67 3939·last commentNode.js 22/24 Vercel Function hangs ~60s then returns INTERNAL_FUNCTION_INVOCATION_FAILEDHello Vercel team, I have a persistent Vercel Functions runtime issue affecting both Preview and Production. Project: dental-clinic-erp Production: dental-clinic-erp-two.vercel.app Production error: 500 INTERNAL_FUNCTION_INVOCATION_FAILED A real Preview Function Invocation shows: Deplo
CFCM·last commentDoes top-level public/ bypass the container catch-all and Fluid Compute?I am running a PHP 8.3 + Apache application using Dockerfile.vercel with Fluid Compute in syd1. Observability shows that static requests such as /assets/*, images, favicons, robots.txt, and sitemap.xml are currently invoking the container /index route. This is significant because the p
Shubham·last commentGetting error for long running tasksI wanted to run some tasks which took more than 300 seconds. I enabled Fluid compute for this. Now when I am executing these tasks I am getting the below error. I am basically running crons using Inngest (inngest.com). Can someone suggest what might be wrong here? Another thing that I o
Anirudh Coontoor·Functions with 1800s (extended-duration beta) rarely reuses instances: ~20× more new instancesTL;DR Under Fluid compute, a function with maxDuration = 1800 starts a new instance roughly every 30 requests. The same code at 300s or 800s starts one every 600–700 requests. Requests routed to those new instances spend ~2.2–3.0s on the platform before the handler runs. This shows up a
Quicktalog·Usage of fluid computeHi all, I am using vercel for quite some time. Since fluid compute was intruduced it was automatically enabled for my app (not sure how). I am now getting closer to 4h of fluide compute in my hobby plan. I am interested how to enable it only for certain functions and when not...
+7
