Hi @.oxyzen were you able to get this fixed? I'm having the same problem. It seems to come from Neon after a cold start

I also need help with this, and that is correct it seems to only happen on cold starts. I don't think this has to do with hot module reload on local env, its also happening deployed in vercel

From neon error docs.

@Gazami crab I managed to find a not very pretty workaround basically by doing retries 1s apart each other until it succeeds or it reaches the maximum retry. I've noticed that it only takes a couple of secs max to warm up the db so this works

Here's a snippet:

const retryQuery = async (
  retries = 3
): Promise<DailyBenchmark[]> => {
  try {
    return await query();
  } catch (err) {
    if (retries === 0) throw err;

    await sleep(1000);
    return await retryQuery(retries - 1);
  }
};

If you find something better, please share it 🙂 I'll be also looking for a better solution. This sounds like an issue with Vercel and Neon though but I may be wrong

I don't know if this count as a fix but I'm running the local dev server with --turbo flag. This works for me and didn't throw any error till now.

It should be fixed guys 🙂