I've deployed my nextjs app on vercell, and thus all the API route handlers work in a serverless fashion.

Some of these handlers process webhook calls, the payload of which requires some processing, which could take a few seconds. And I want to immediately send back a 200 to the webhook provider to notify them so that they don't keep retrying.

So the way I'm doing this is, after verifying the webhook payload, I call another next.js route handler API using fetch, offload the processing to that route, and then return a 200.

This works fine in local development when it's pretty much a stateful node backend continuously running.

But when deployed on the edge, the fetch call to the other route handler never gets made. Sometimes I get fetch failed error, while sometimes I don't get any error, but I just can't see the other endpoint being hit at all (in any case).

How can I resolve this situation?