any ideas on what could be causing this?
# prisma-whats-new
d
any ideas on what could be causing this?
just checked and getting the same issue from a fresh
prisma init
node advanced boilerplate
n
it sounds like you are using an authorization header that encodes a user id to a user that is not present in your service.