Hey all, I'm running in to the strangest issue. I have a very simple Yoga back end that I've set up to play around with some graphQL concepts and it's working great locally. However when I deploy to now.sh I'm seeing an issue where upon creating an entry it's actually creating two entries in the database each with a unique id. I've tested this on the playground of my deployed server to rule out the front end being an issue and I'm seeing the same thing. Running:

mutation  {
  createListItem(title:"this is a test of a new item") {
    id
    title
  }
}

Returns one item. But then, when running:

query {
  listItems(first:4 skip:0){
    id
    title
  }
}

I see two items returned with the same title and different ID's. My mutation is about as simple as it gets

createListItem(parent, args, context, info) {
      return context.prisma.createListItem({ title: filter.clean(args.title) })
    }

so I'm just not sure what could be going wrong here. Again, it's working fine locally and the only real difference between the two is the NODE_ENV. Both the local and deployed versions are connecting to the same Prisma demo database. If I go directly to the playground of the prisma database I don't get the same issue. Any help figuring out where to start would be appreciated beyond belief

This sounds like a bug we currently have in Prisma client: https://github.com/prisma/prisma/issues/3210 We are on it 👍 sorry for the confusion 🙂

Oh thank goodness, that was driving me crazy! thanks for the heads up 🙂