Prisma ORM Error P2025: Record not found

Identify: does your log match?

PrismaClientKnownRequestError:
Invalid `prisma.post.update()` invocation in
/app/src/routes/posts.ts:41:28

An operation failed because it depends on one or more records that were required but not found. No record was found for an update.
  code: 'P2025',
  meta: { modelName: 'Post', cause: 'Record to update not found.' }

1. High

   Stale or wrong id from client

   The row was deleted by another request, or the id belongs to another tenant filtered out by where.

2. Medium

   Extra filters in a unique where

   where: { id, authorId } on update requires both to match. A non-owner request finds no row and throws P2025.

3. Low

   Nested connect to missing relation

   connect: { id } on a relation whose target row does not exist also raises P2025.

Fix

const post = await prisma.post.delete({ where: { id } });
return Response.json(post);

import { Prisma } from '@prisma/client';

try {
  const post = await prisma.post.delete({ where: { id } });
  return Response.json(post);
} catch (e) {
  if (e instanceof Prisma.PrismaClientKnownRequestError && e.code === 'P2025') {
    return Response.json({ error: 'Not found' }, { status: 404 });
  }
  throw e;
}

Verify: reproduce it on purpose

$ node -e "const {PrismaClient}=require('@prisma/client');new PrismaClient().user.delete({where:{id:-1}}).catch(e=>console.log(e.code, e.meta))"

Prevent

• Use findUnique + null check for reads, not findUniqueOrThrow, when 404 is expected.
• Scope where clauses by tenant and treat P2025 as 404.
• Make delete endpoints idempotent with deleteMany.