Urgent: Product GraphQL API bug? Suddenly getting "Variable $input of type ProductVariantInput! was provided invalid value for inventoryItem.sku (Field is not defined on InventoryItemInput)"

GraphQL Admin API Troubleshooting
,
1

As of this morning we are suddenly getting this error on 2024-07 when creating new products.

1 Like
2

We also started seeing errors at 15:00 UTC exactly when calling the inventorySetQuantities mutation in the GraphQL API:

"one or more errors returned from shopify set inventory level mutation: Field 'inventorySetQuantities' doesn't exist on type 'Mutation'"

We are also on 2024-07, though we’re in the process of migrating off of it

3

Thanks @ktbishop for confirming it’s not just us. Unfortunately we can’t yet migrate to 2024-10 because of this: productVariantsBulkCreate deletes default title variant even when using default behaviour

4

@Liam-Shopify Any chance someone can look into this? This seems like a pretty big issue to pop up out of nowhere.

Also seeing an issue that started at the exact same time (15:00 UTC) where we pull assignedFulfillmentOrders, which returns a list of FulfillmentOrders assigned to our location, but a second or two later when we pull one FulfillmentOrder from that list by the id, the GraphQL API says that Fulfillment Order doesn’t exist

5

We patched this for now by not setting a sku field when using this mutation - but this isn’t a viable long term solution.

6

@ktbishop for your assignedFulfillmentOrders bug which API version are you on there?

7

Currently on 2024-07 like you

1 Like
8

Well, since the issue persisted so long with no further updates from Shopify I was finally forced to just push our API version to 2024-10 (with no integration testing or anything) and that got us around the issue, so it does appear to be limited to just 2024-07. I’ll just have to deal with any bugs that come up as a result of that forced migration.

I know you mentioned you weren’t able to migrate just yet so this probably doesn’t help you out any, but if anyone else comes along (shopify or otherwise) I hope they see this. Though, hopefully the issue won’t persist much longer and someone at Shopify will learn a valuable lesson about pushing breaking changes out without some forewarning.

1 Like
9

@Liam-Shopify are you here? We could use support on this, as well as this blocking issue where you are tagged: productVariantsBulkCreate deletes default title variant even when using default behaviour

10

looked like this error was solved for a few hours, but it’s back again.

11

Hi folks,

It looks like this issue may have been related to a recent schema change - but it should only be affecting API versions 2024-07 or less. If you’re seeing this issue on 2024-10 can you share a sample mutation that I can check on our side?

12

Also started seeing the below on 2024-07 out of nowhere:

Variable $input of type DraftOrderInput! was provided invalid value for lineItems.0.appliedDiscount.amountWithCurrency (Field is not defined on DraftOrderAppliedDiscountInput)

Anyone else still having issues?

13

@Liam-Shopify can you please confirm if the team is working to resolve these issues for 2024-07? It was fixed per Shopify Status around 00:00 UTC and it started again in the early morning hours.

1 Like
14

Hey @KyleG-Shopify,

I saw your reply to the below thread and wanted to add you here since I think this is the same issue.

Any help on this would be greatly appreciated.

15

From connecting with our teams internally it looks like this issue is only impacting the 2024-07 API version which is just recently deprecated and unsupported. Our advice is to switch to a more recent version - 2025-07 if possible.

1 Like
16

@Liam-Shopify Just to clarify - is Shopify’s official stance that this issue won’t be fixed, even though:

  1. This same bug (or at least whatever was causing it) triggered a public Shopify Status incident on Wednesday, which was acknowledged and eventually resolved
  2. The same API error reoccurred only a few hours later
  3. Merchants and partners are still actively relying on 2024-07, given that newer versions have unresolved issues, for example this thread in which you were included: productVariantsBulkCreate deletes default title variant even when using default behaviour

This response puts app developers and merchants in a difficult position as we’re being asked to force upgrade to newer versions that introduce their own bugs, while support is being dropped for versions still actively in use due to those very bugs.

We’d really appreciate a more constructive and solution-oriented response here as this is interrupting merchants’ businesses and undermining confidence in the API versioning lifecycle.

1 Like
17

@Liam-Shopify Why aren’t these requests falling forward to 2024-10? Is Shopify changing how it handles old versions? This is straight from the API docs (linked):

However, if your app uses a stable version that is no longer supported, then Shopify falls forward and responds to your request with the same behavior as the oldest supported stable version. For example, when Shopify removes 2023-07 , API requests to version 2023-07 will be served version 2023-10 , because that will be the oldest supported stable version.