Inconsistency in field TRACKED between Graphql and API

[Mete]

{

  inventoryItem(id: "gid://shopify/InventoryItem/41355176935468") {

    tracked

  }

}

returns

{

"data": {

"inventoryItem": {

"tracked": true

        }

    },

"extensions": {

"cost": {

"requestedQueryCost": 1,

"actualQueryCost": 1,

"throttleStatus": {

"maximumAvailable": 1000.0,

"currentlyAvailable": 999,

"restoreRate": 50.0

            }

        }

    }

}

But API returns

{

"inventory_item": {

"id": 41355176935468,

"sku": "",

"created_at": "2021-03-05T12:25:27+03:00",

"updated_at": "2021-03-17T13:33:38+03:00",

"requires_shipping": true,

"cost": null,

"country_code_of_origin": null,

"province_code_of_origin": null,

"harmonized_system_code": null,

"tracked": false,

"country_harmonized_system_codes": [],

"admin_graphql_api_id": "gid://shopify/InventoryItem/41355176935468"

    }

}

I would expect the second one is correct but why graphql returns such a response.

Another item with the same problem:

gid://shopify/InventoryItem/41355176902700

[_JCC_]

Hey @Mete ,

Happy to help out. Are you able to still produce this issue. If so, could you provide the x-request-id found in the response headers of the requests so we can review our logs.

Regards,

John

[Mete]

---

@_JCC_ wrote:

Hey @Mete ,

Happy to help out. Are you able to still produce this issue. If so, could you provide the x-request-id found in the response headers of the requests so we can review our logs.

Regards,

John

---

Hey @_JCC_ ,

Unfortunately I forgot to save x-request-id. Now we can't reproduce it and they have been fixed suddenly.

[_JCC_]

Hey @Mete ,

Thanks for the update. If you notice the behaviour again let me know and I'll take a look.

Regards,

John