In a serverless environment, you're only billed for how long your function is running. However, in this case the function never terminates even after request it

In a serverless environment, you're only billed for how long your function is running. However, in this case the function never terminates even after request it handles completed. I suspect the user made a mistake of deploying a traditional web app (where there is a main process that route requests and wait indefinitely for next requests) instead of deploying individual "function" that terminates gracefully after handling the request. Seems to be an honest mistake to make for first time user. In other platform, his process will be killed by the timeout limit (serverless platform usually has a strict timeout limit) but for some reason, in vercell it keep on running forever and racked up a huge bill.