Can someone help me troubleshoot why I am getting the following error when running a basic query on the client playground? Error:

Cannot return null for non-nullable field DeviceConfig.device.

Datamodel

type Device {
    ...
    model: String! @unique
    ...
    configs: [DeviceConfig] @relation(name: "DeviceConfigs", onDelete: CASCADE)
  }

  type DeviceConfig {
    id: ID! @unique
    device: Device! @relation(name: "DeviceConfigs", onDelete: SET_NULL)
    name: String!
    ...
  }

Query

{
  deviceConfig(id:"cjqigyian00ef0d206tg116k5"){
    name
    id
    device{
      model
    }
  }
}

Resolver

deviceConfig: async (parent, { id }, context, info) => context.prisma.deviceConfig({ id }, info)

Result

{
  "data": null,
  "errors": [
    {
      "message": "Cannot return null for non-nullable field DeviceConfig.device.",
      "locations": [
        {
          "line": 5,
          "column": 5
        }
      ],
      "path": [
        "deviceConfig",
        "device"
      ]
    }
  ]
}

--- When I run the following query on the Prisma API playground it returns Query

{
  deviceConfig(where:{id:"cjqigyian00ef0d206tg116k5"}){
    name
    id
    device{
      id
      model
    }
  }
}

Result

{
  "data": {
    "deviceConfig": {
      "name": "Standard",
      "id": "cjqigyian00ef0d206tg116k5",
      "device": {
        "id": "cjqigxzs600e60d20sdw38x7p",
        "model": "7530"
      }
    }
  }
}

what if you remove async from this line:

deviceConfig: async (parent, { id }, context, info) => context.prisma.deviceConfig({ id }, info)

(edited) there is no await in the function

Thanks for the suggestion, but same result.

I am not familiar with the syntax of "onDelete" (new feature I haven't caught onto? - I finished writing my datamodel six months ago) It seems suspicious that you have "onDelete: SET_NULL" for a required ("Device!") field. As for the different behavior between resolver results and prisma api results... that is odd.