Skip to content
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

Open
johnkw opened this issue Dec 17, 2024 · 8 comments
Assignees
Labels
FBA Inbound Issues related to FBA Inbound APIs Support Issue Issues that requires a Developer Support case

Comments

@johnkw
Copy link

johnkw commented Dec 17, 2024

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.

@johnkw
Copy link
Author

johnkw commented Dec 17, 2024

After several Workflow cancel/delete and start over, it eventually worked. So it doesn't always fail, but it fails quite a lot.

@johnkw johnkw changed the title confirmTransportationOptions always fails with InternalServerError for multi-shipment placement confirmTransportationOptions frequently fails with InternalServerError for multi-shipment placement Dec 17, 2024
@LennyPu
Copy link

LennyPu commented Dec 18, 2024

I also have the same problem with single shipment, whenever i chosen the UPS

@puppsupr
Copy link

Hi @johnkw, @LennyPu,
In order to correctly resolve this issue, Please open a support case following the guidance here so we can pursue the investigation as additional details are required from your end.

@puppsupr puppsupr self-assigned this Dec 19, 2024
@puppsupr puppsupr added closing soon This issue will be closed soon Support Issue Issues that requires a Developer Support case FBA Inbound Issues related to FBA Inbound APIs labels Dec 19, 2024
@johnkw
Copy link
Author

johnkw commented Dec 19, 2024

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.

@github-actions github-actions bot removed the closing soon This issue will be closed soon label Dec 19, 2024
@puppsupr
Copy link

Hi @johnkw,
Can you provide the case number ?

@johnkw
Copy link
Author

johnkw commented Dec 24, 2024

16853613761

@lightningja
Copy link

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.

@puppsupr
Copy link

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FBA Inbound Issues related to FBA Inbound APIs Support Issue Issues that requires a Developer Support case
Projects
None yet
Development

No branches or pull requests

4 participants