``` { "data": { "updateOrder": null }, "...
# orm-help
c
Copy code
{
  "data": {
    "updateOrder": null
  },
  "errors": [
    {
      "locations": [],
      "message": "There can be only one input field named 'boolean'.",
      "path": [
        "updateOrder"
      ]
    }
  ]
}
i’m try to run this mutation
Copy code
mutation {
  updateOrder(
    where: {
      id: "cjdg5pgbcl17b0134orwjp082"
    }
    data: {
      status: DONE
    }
  ) {
    id
    status
  }
}
n
it seems to be an issue with using
updated_fields
in a subscription: https://github.com/prismagraphql/prisma/issues/2333
are you doing that?
c
i’ve removed a subscription from
prisma.yml
here is my
prisma.yml
Copy code
# endpoint: <http://localhost:4466/prisma/${env:PRISMA_STAGE}>

endpoint: ${env:PRISMA_ENDPOINT}
datamodel: 
  - prisma/datamodel.graphql
  - prisma/enums.graphql

hooks:
  post-deploy:
    - graphql get-schema --project database
    - graphql prepare
    - cp ../core/src/generated/prisma.graphql ../microserver/generated/prisma.graphql

# subscriptions:
#   orderStatusChanged:
#     webhook: https://....
#     query: core/src/subscriptions/orderStatusChanged.graphql

# secret: ${env:PRISMA_SECRET}
i’ve solved the issue by remove
updated_fields
in
orderStatusChanged.graphql
. i thought, it should disable if it was removed from
prisma.yml
. thx @nilan
n
@ChinCluBi did you deploy after commenting the subscription out?
c
yep, i did .. twice
n
sounds like an issue with deploys not picking up the removal of subscriptions correctly - could you create a new issue report for that here: https://github.com/graphcool/prisma/? 🙂
c
sure
😄
n
🙏