It seems to be working again after around 30min. Do you have any information about what happened ?

    at ei.request (/app/node_modules/@prisma/client/runtime/library.js:121:6300)
  meta: { modelName: 'User', table: 'public.User' },
    at async a (/app/node_modules/@prisma/client/runtime/library.js:130:9551)
  clientVersion: '6.19.0'
    at async main (/app/dist/prisma/seed.js:9:19) {
}
  code: 'P2021',
Invalid `prisma.user.upsert()` invocation in
/app/dist/prisma/seed.js:9:37
  6 async function main() {
  7     console.log('👤 Creating users...');
  8     const hashedAdminPassword = await bcrypt.hash('admin123', 15);
→ 9     const admin = await prisma.user.upsert(
The table `public.User` does not exist in the current database.
❌ Error seeding database: PrismaClientKnownRequestError: 

Looks like your application had trouble seeding the database and that caused it to fail?

I am also seeing it is working now. I see that postgres was redeployed a few times around 14 hours ago. But I'm not sure why the database was unavailable on the private network at that time.

Yes, when database was inaccessible, as this is my “integration” environment, I tried wiping it to make it works. I met the database problem before the seeding lines, around 08:30:18 UTC+2 on Dec. 11.

The logs you sent are from my backend api which tried to seed database before creating the structure, but I solved it a few minutes later.

Before that, I had a few errors, as shown in attachments.