I tried the same API call on my local development server and building and running it locally connected to the remote DB and all were able to receive and load the data from Turso, so I don’t think it’s an issue from their response.
I added console logs after each line of the function and the function starts and gets to the call requesting data from Turso after which it dies, now it’s receiving a 404, function /_not-found.
To test these changes, I am using the Vercel preview URLs. However, since the calls are working on some pages and for some sizes of requests, I don’t think it’s the URL as I would imagine that would affect across the entire site for all requests.