[SOLVED] Getting the 'INVALID_OPERATION' error

[peterstarling]

I have…

• [x] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

• [ ] Regression (a behavior that stopped working in a new release)
• [x] Bug report
• [ ] Performance issue
• [ ] Documentation issue or request

Current behavior

When I make the following query

query FetchTeam($id: String!) {
   findTeamsContent(id: $id) {
      id
   }
}

with these variables

{
  "id": "6b5802ec-bacd-43da-8280-2a48b8a0a3a4"
}

I get

{
  "errors": [
    {
      "message": "Error trying to resolve field 'findTeamsContent'.",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "findTeamsContent"
      ],
      "extensions": {
        "code": "INVALID_OPERATION",
        "codes": [
          "INVALID_OPERATION"
        ]
      }
    }
  ],
  "data": {
    "findTeamsContent": null
  }
}

Expected behavior

It looks like this entity does not exist so it should return null.

Minimal reproduction of the problem

see above

Environment

• [ ] Self hosted with docker
• [ ] Self hosted with IIS
• [ ] Self hosted with other version
• [x] Cloud version

Version: [VERSION]

Browser:

• [ ] Chrome (desktop)
• [ ] Chrome (Android)
• [ ] Chrome (iOS)
• [ ] Firefox
• [ ] Safari (desktop)
• [ ] Safari (iOS)
• [ ] IE
• [ ] Edge

Others:

There are other IDs which cause the same failure , for instance 16f2c6c7-4994-4d77-ba0a-d3c5214e5f2e

APP NAME: asap-hub

[Sebastian]

I can reproduce it and will provide a fix.

Edit: The problem exists, when the content exists, but is from another schema.

[Sebastian]

Solved, but not deployed.