I posted about this yesterday and didn’t get a response, I’m still struggling with the problem today. I’m getting an error in playground when trying to submit a mutation that says:

Whoops. Looks like an internal server error. Search your cluster logs for request ID: the-id

Running

prisma cluster logs

shows “Loading logs from docker…“, a checkmark after a few seconds, then shows “Attaching to” and immediately ends with no error. Most of my mutations/queries work fine. Nothing has changed in my project recently, I had to step away from it for a few weeks and now this problem has arisen when there was none before. I’ve tried nuking my cluster/database a few times now in an attempt to fix it to no avail.

can you use

docker logs -f <container id>

instead? 🙂

Yes! That worked, and from the logs I can see it’s apparently an error related to some Json data:

InvalidValueForScalarType

. I suspected that was the problem. But now I don’t know why that would be happening, heh

Please share some more context when this happens.

It looks alright to me, and this was working last time I was on this project just fine. What would cause an error like that to appear in the logs but validate in Playground?

Is it a specific query or mutation?

Yes, I mentioned in the original question that most of my mutations/queries work fine, it looks like it’s only mutations that use the Json scalar. I can’t query anything with Json at the moment to test since there’s nothing in the database anymore, but that’s definitely the problem.

what's your server version?

I’m currently running 1.7.3

Ahhhh, so if there’s issues with the Json it’s not getting properly reported in Playground? That would explain it. I’ll keep bashing away at it then. Thanks a bunch

Hm I'm not sure about the Playground part 🙂