-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
confirmTransportationOptions frequently fails with InternalServerError for multi-shipment placement #4436
Comments
After several Workflow cancel/delete and start over, it eventually worked. So it doesn't always fail, but it fails quite a lot. |
I also have the same problem with single shipment, whenever i chosen the UPS |
Hi @johnkw, @LennyPu, |
Well I did already open a support case days ago but there's been no response. The important thing for anyone that finds this ticket to know is: keep deleting the entire workflow and trying again. It seems it's possible to eventually get it to work. |
Hi @johnkw, |
16853613761 |
second that. created several support cases but you kept asking for more info without actually investigating it. I've provided the request Id, inbound plan Id and operation Id. |
Hi @johnkw, the case 16853613761 is being actively investigated, you see more details over the case once the investigation is done. @lightningja, can you please provide your case number as well ? |
The
https://sellingpartnerapi-na.amazon.com/inbound/fba/2024-03-20/operations/...
call fails with:{"operationStatus":"FAILED","operationId":"[...]","operation":"confirmTransportationOptions","operationProblems":[{"severity":"ERROR","code":"InternalServerError","message":"ERROR: Something went wrong. Please try again later."}]}
This is essentially a duplicate of bug #4144 but that one was closed without any resolution or workarounds being posted. It was also mentioned in bug #4133 and in #3951 (comment)
Deleting the entire Workflow and trying again doesn't seem to help at all, it just keeps happening.
The text was updated successfully, but these errors were encountered: