Prisma Data Proxy Errors- Data Proxy started to throw the following error this morning: `Invalid

prisma.user.findMany()

invocation:\n\n\n Failed to validate the query:

Field does not exist on enclosing type.

at `Query.findManyUser`"` on a working deploy. We tried to redeploy using Prisma v3.7.0 but we are getting the following error `Invalid

prisma.user.findMany()

invocation:\n\n\n Invalid value \"undefined\" for header \"transactionId\"","reason":{"errorType":"Error","errorMessage":"\nInvalid

prisma.user.findMany()

invocation:\n\n\n Invalid value \"undefined\" for header \"transactionId\"","code":"ERR_HTTP_INVALID_HEADER_VALUE","clientVersion":"3.6.0"` We reached out on Data Proxy support but didn't heard back for the past 4 hours so I decided to bring the conversation here to know if someone else is facing these issues and was able to fix it.

Thanks for letting us know, Rodrigo! I’ve forwarded this to the platform team so they hopefully can look into it soon! (Some of their engineers are on holidays atm though, so it might take a bit longer for us to react here 🙏).

Thanks for the update @nikolasburk!

Hey Rodrigo, are you using the

interactiveTransactions

feature in the app? Transactions are not supported by the Data Proxy in case you’re using them here, so that might be the issue?

@nikolasburk We are using

interactiveTransactions

but not in that specific query that runs through data proxy

Weird that those endpoints were not even using interactive transactions but it was erroring out

Yeah, that does seem odd! Our engineers will certainly look into this, thanks for reporting!! 🙏

@nikolasburk That solved it! Really weird that it happened on a deploy we had that was not using

interactiveTransactions

. I think it may have something to do with schema (re)upload to the dataproxy