Prisma

```
{
  "error": {
    "message": "The provided query doesn't include any known model name. Please check for the latest subscriptions API."
  }
}
```
does anyone know how to fix this? I got it with the same structure as in <https://github.com/nikolasburk/subscriptions>, only happens after I do `prisma deploy` (locally), if I run a fresh instance (only with `docker-compose up -d`) it stay subscribed

for some reason it works on playground with Prisma but doesn't work when I call it through server

Please share
- your datamodel
- your application schema
- the subscription resolver in question
- the subscription query

<@U0RQY0KK5>: <https://gist.github.com/lucasbento/01882570e4b3fe08e8449914eed2dce5>

tried a bunch of stuff (restarting, cleaning everything, updating deps) and nothing changed, I have no clue on why this is happening

does this subscription work when running against the Prisma API directly:
```
subscription {
  chatMessage(where: {
    mutation_in: [CREATED, UPDATED]
  }) {
    mutation
    updatedFields
    node {
      id
      text
    }
  }
}
```

I’m not able to test it right now but I recall that it works fine without the `where` condition, I can test it again today at night

<@U0RQY0KK5>: I was trying with that same exact query before and it's working directly with prisma

I think it's worth noting that doing it through the server before `prisma deploy` apparently works (at least keeps listening on playground) and throws error after running `prisma deploy`

just ran that query on prisma and works fine

Ok, I see! Could you please share your code in a new report at the prisma-binding repo? :slightly_smiling_face:

I'll put together a small repro code in an issue there and will let you know, thanks <@U0RQY0KK5>!

hey <@U0RQY0KK5>, I created a reproduction code here: <https://github.com/lucasbento/prisma-binding-issue>

but I don't think it's related to `prisma-binding`, I tried putting something else inside of `subscription` resolver but I still have the same problem