system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Anshuman Bhardwaj Hi @integrations01-takeb, I'm sorry you are facing this issue. Can you confirm if you are getting a SIGTERM signal? When a function instance is scaled down, the container receives a SIGTERM signal with a 30 seconds grace period to clean up before being forcefully terminated. Try checking for the SIGTERM to see if the vercel.com/docs/functions/functions-api-reference#sigterm-signal Additionally, the 5-minute threshold represents the maximum idle time before shutdown rather than a guaranteed minimum warm lifespan, meaning instances can occasionally be recycled earlier by the underlying orchestra

William Molina Hello Vercel team, I also need clarification about git.deploymentEnabled on the first push that creates a new branch. I use the Hobby plan and am asking about documented platform behavior, not requesting any account changes. Assume an existing Git-connected project and a new non-production branch. The first pushed commit contains a valid vercel.json at the effective project root, with git.deploymentEnabled set to false for that exact branch and no matching true rule. Could Vercel staff clarify: Does Vercel evaluate vercel.json from that first pushed commit before creating a deployment record o

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Guillaume Quick update: my 30-day Fluid Active CPU usage is now back under the Hobby limit (3h 57m / 4h), and it keeps dropping since nothing has run since Oct 30. The job has also been moved off Vercel entirely, so it won’t consume Vercel CPU anymore. Could you please unpause the team before Nov 29? Thanks!

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Muthumohammed810 5526 Hello Vercel Team, I am facing an issue while trying to upgrade my existing Production Blob Store to OIDC. Whenever I click the "Upgrade to OIDC" option, I immediately receive the error: "An unexpected internal error occurred" I have already refreshed the page and tried again, but the issue persists. My live website is currently working with the existing Blob read-write token authentication. Could you please investigate this issue and guide me on how to safely enable OIDC without affecting my live website or existing Blob data? Thank you for your help.