Foreign key constraint failed on the field: `authorId`

TL;DR: Look up the parent record before you create the child. If the parent lookup misses, return a clear not-found message instead of letting the database throw P2003. The error means the id you are linking to does not exist.

Foreign key constraint failed on the field: `authorId`

Steps

1. Read the field name in the error. authorId tells you the relation that failed: the author you referenced does not exist.

2. Verify the parent exists before creating the child:

   const author = await prisma.user.findUnique({ where: { id: input.authorId } })
   if (!author) {
     return { ok: false, message: 'Author not found.' }
   }
   await prisma.post.create({ data URIs { title: input.title, authorId: input.authorId } })

   Expected: a bad author id returns your clean message; a good one creates the post.

3. Still catch P2003 as a backstop for races (the parent can be deleted between your check and your write):

   } catch (e) {
     if (e instanceof PrismaClientKnownRequestError && e.code === 'P2003') {
       return { ok: false, message: 'The linked record no longer exists.' }
     }
     throw e
   }

   Expected: concurrent deletes produce a friendly message, not a 500.

When to use

• The exact code is P2003 on a create, update, or connect that references another record
• The referenced id comes from user input, a URL param, or another service

When not to use

• P2002: that is a duplicate value, not a missing parent
• You are deleting a parent with children: that is a cascade / restrict policy question, set onDelete in the schema

Compatibility

Prisma Client 4.x through 6.x. All relational providers.

Variant phrasing: P2003 on connect: { id } in a nested write

Same fix: verify the id exists before the nested write, or catch P2003 around it.

Variant phrasing: P2003 in a seed script

Seeds run in order; the parent seed must run (and commit) before the child seed. Check your seed order.

Why it happens

The foreign key in the database guarantees the child always points at a real parent row. When the app sends an id that is not there (typo, stale client state, deleted parent), the database rejects the write and Prisma reports P2003. Checking first turns a database rejection into an application-level message.

Edge cases

• onDelete: Cascade vs Restrict: deleting a parent with children fails differently; choose the policy your domain needs.
• UUID vs integer ids: a malformed id string can fail parsing before it ever reaches the constraint check.
• Multi-tenant apps: the parent may exist but belong to another tenant; scope the lookup by tenant, not just by id.

A fuel quota management backend hit P2003 when creating vehicle records that referenced a user id that did not exist. The fix merged into the codebase: before creating the child record, look up the parent with findUnique, and return a clear 'user not found' error when the lookup misses instead of letting the database reject the write. After the change, bad references produce a clean application-level message and valid writes proceed. Source: https://github.com/im-ushan-ikshana/fuel-quota-management/blob/HEAD/backend/docs/PRISMAERRORHANDLING.md