Warehouse_product_delete "Unexpected Error"

Capture2
Capture

Hello, I am getting this unexpected error when I run the warehouse_product_delete mutation, there seems to be an issue. I am able to delete the warehouse products manually via the web app though.

Hello @kolbykskk!
Thank you for reaching out to us.
We are now looking into the issue, the team is tracing the Unexpected Error you are getting.
I will get back to you as soon as I have an update.
Have a nice day!
Tomas

1 Like

Hello @kolbykskk!
I’ve been running some tests and I’m experiencing the same issue. I will escalate the issue and let you know when I have an update.
Have a great weekend!
Tomas

1 Like

Hey, just following up here as well.

Hello @kolbykskk!
I have escalated this issue again. I will let you know as soon as I have an update,
Have a nice day!
Tomas

1 Like

Hey, just following up here. We really need to get this working if we can

Hello @kolbykskk!
Apologies for the late answer.
We are currently under code freeze until 12/27/2021.
I won’t be able to provide any updates on this issue until we are out of it.
Thank you for understanding.
Best regards,
TomasFD

Hey, just following up here

Hello @kolbykskk!

I will request an update on this. I’ll let you know as soon as I have an answer.

Have a nice day!
TomasFD

Hi, just following up on this issue. We’re still seeing the unexpected error for all of these requests

Hey @kolbykskk,

Going to push for an update here. I’ll let you know as the updates come in.
Your patience is very much appreciated!

Best,
RayanP

1 Like

Hey, it’s been a very long time on this, where is it currently standing?

The endpoint still throws an error.

Hey @kolbykskk,

Thanks for hanging in there!

This one is currently in our Engineers queue. We actually supplemented the ticket with new examples about two weeks ago, so I think progress will made here soon.

We appreciate your patience!

Best,
RayanP

Any updates? Our workaround was to use the -on_hand sort key with warehouse_products to keep the irrelevant product at the end but that now throws an error too so it must have been recently removed. We really need the delete mutation to work.

Hey @kolbykskk,

Thanks for reaching out!

We currently have no updates to share but I’ll reach out to the team about getting some movement here.
Would you mind sharing an example or request_id of the work around query you mentioned?

Please let me know if you have any questions or concerns.

Best,
RayanP

Sure, here is the request ID

65df31f65367c4191f491019

This has been erroring for years at this point