"message": "Unknown operation named \"undefined\"."

[songololo]

I'm testing / debugging resolvers using GraphiQL. At times, seemingly prompted by restarting the backend app, I'll start getting responses like this:

{
  "errors": [
    {
      "message": "Unknown operation named \"undefined\"."
    }
  ]
}

Restarting the app or refreshing the GraphiQL page do not fix the error. However, cutting the query and pasting it back into the query window seems to resolve the issue.

Thanks.

[wincent]

Thanks for submitting the report, @Shongololo. However, I think we might need a more concrete repro recipe. I know this might be hard, if the issue is intermittent; do you see it on every backend restart? Can you provide a little more detail about what versions you are running and how?

[salujaharkirat]

Even i facing this issue while calling mutations on my sample project.

Sharing few details :-

Mutation Query

mutation{
 toggleTodo(input:{
  id:"0"
}){
  todo{
    id
  }
}
}

Schema.js

const GraphQLChangeTodoStatusMutation = mutationWithClientMutationId({
  name : 'ToggleTodoStatus',
  description : 'Toggle status of todo',
  inputFields : {
    id: { type: new GraphQLNonNull(GraphQLID) },
  },
   outputFields: {
     todo: {
      type: todoType,
      resolve: ({localTodoId}) => getTodo(localTodoId),
    },
  },
  mutateAndGetPayload: ({id}) => {
   const localTodoId = fromGlobalId(id).id;
   toggleTodo(localTodoId);
   return {localTodoId};
 },
})

const Mutation = new GraphQLObjectType({
  name: 'Mutation',
  fields : {
    toggleTodo: GraphQLChangeTodoStatusMutation
  }
})

const Schema = new GraphQLSchema({
  query  : queryType,
  mutation : Mutation
})

Mock data

class Todo {}

let nextTodoId = 0

const todosById = []

addTodo('First task',false)
addTodo('Second task',false)

function addTodo(text,complete){
  const todo = new Todo()
  todo.complete = complete
  todo.id = `${nextTodoId++}`;
  todo.text = text;
  todosById.push(todo)
  return todo.id
}

function getTodos(){
  return todosById
}

function getTodo(id){
  return todosById[id]
}

function toggleTodo(id){
    todosById.map(function(todo,index){
    if(todo.id === id ){
    todo.complete = !todo.complete
    }
  })
}

module.exports = {
  Todo,
  addTodo,
  getTodos,
  toggleTodo
}

[asiandrummer]

This happens when GraphiQL is trying to figure out which operation under the operationName it wants to run, as the query editor supports having multiple query contexts and running each query by specifying which one.

Are there some steps we can follow to reproduce the issue?

[leebyron]

I'm not exactly sure what the root issue is, but I think this is due to saving state between runs. localStorage coerces everything to a String before saving it, so setting undefined results in getting "undefined".

[kastermester]

I still hit this issue when using unnamed queries/mutations/subscriptions. The issue arises when entering a query, like:

mutation {
  someMutation(input: {
    clientMutationId: ""
  }) {
    clientMutationId
  }
}

If one enters this query, and executes it - everything works as intended. From here, a second reload will yield the error. If doing the exact same query but naming the operation, like this:

mutation MyMutation {
  someMutation(input: {
    clientMutationId: ""
  }) {
    clientMutationId
  }
}

Then no error occours.

EDIT: This is GraphIQL 0.10.1

[mairatma]

Just confirming that I'm having the same problem @kastermester mentioned here. It's pretty annoying and really easy to reproduce, you just need to: run a unnamed mutation, refresh the page and run it again. I'm using the graphiql that graphql-server-express renders, which seems to be at 0.10.2.

[mike-marcacci]

I run into this from time to time as well. @leebyron is definitely correct that the string "undefined" is getting serialized in both localStorage and the search params:

My suspicion is that the latter (the search param) is the real culprit here, as simply deleting it resolves the issue, even though undefined remains in localStorage.

[Durisvk]

I have the same problem, how long would it take to fix this on your side? Are you working on it?