Issue with ProductBundleUpdate Mutation When Attaching Components

New GraphQL Product APIs
1

I’m encountering an issue when trying to attach components to an existing product using the new productBundleUpdate mutation. This operation consistently fails with a generic error that provides no actionable information:

{
  'code': 'GENERIC_ERROR', 
  'field': None, 
  'message': 'Validation failed: '
}

What I’ve Tried

  • The empty validation message ('Validation failed: ') doesn’t provide any clues about what’s failing
  • I’ve confirmed my input data is correctly formatted according to the API documentation
  • I’ve verified that all referenced product IDs exist and are valid
  • Double-checked permissions to ensure I have the necessary access rights

Previous Method Worked

Interestingly, before the introduction of the new productBundleUpdate mutation, I was able to add components to existing products without any issues using the previous method productVariantRelationshipBulkUpdate.

Questions for the Community

  1. Has anyone else encountered this generic validation error when using productBundleUpdate?
  2. Are there any common validation pitfalls that aren’t clearly documented?
  3. Is there a way to get more detailed error information to understand what’s failing?
  4. Are there any workarounds or alternative approaches that would allow me to attach components to existing products?

Any insights or suggestions would be greatly appreciated!

2

Hi, do you have an example of what mutation are you sending and the payload? productBundleUpdate should work normally.

I just tested on my end and it works. Make sure you are sending the correct payload structure.

I followed this guide as an example.

3

Thanks Thomas for testing it.

When I tried doing it on my dev store. I was able to create it as well.

But I have faced this issue a couple of times when doing this for a live brand on a live product.

Sadly, I don’t have anymore information as to what is the difference between the live product and dev product but happens every time when this feature is actually required by the brands.

I’ll update this post if I find more information or if you are able to find any case where it might be an issue. Feel free to update here.