amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
608 stars 731 forks source link

Issue with confirmTransportationOptions on inboud shipment. #4162

Closed hellokids86 closed 1 month ago

hellokids86 commented 1 month ago

Hello,
I am trying to confirm transport options on an inbound shipment via the API. I receive the following error back after checking the operation status. It works on and off depending on the options I choose when confirming transportation. Not sure what is wrong with my request.

{ "operation": "confirmTransportationOptions", "operationId": "a41cc4e8-9235-4472-b832-3d3931cedcf6", "operationProblems": [ { "code": "BadRequest", "message": "ERROR: Fail to execute CONFIRM_CARRIERS API with errors.", "severity": "ERROR" } ], "operationStatus": "FAILED" }

hellokids86 commented 1 month ago

The issue seems to be with confirming Amazon Partnered LTL with confirmTransportationOptions .

xyloneX commented 1 month ago

The issue seems to be with confirming Amazon Partnered LTL with confirmTransportationOptions .

SPD Not support?

hellokids86 commented 1 month ago

Is SPD for Small Parcel? If so, this is working, however LTL by Amazon Partnered Carriers is not working.

xyloneX commented 1 month ago

I issue encountered this problem, just recreate it

jackmin-sw commented 1 month ago

the same issue, just return ERROR: Fail to execute CONFIRM_CARRIERS API with errors, the api works well before today. I view the info in the console, it shows that it has multiple delivery address. and when we create shipment with only one box, then we can pass the whole flow. Not sure it is because of multiple delivery address lead this issue?

emakunin commented 1 month ago

+1

Note: It seems to be a duplicate of https://github.com/amzn/selling-partner-api-models/issues/4048

I use SPD shipments, details are in the linked ticket.

puppsupr commented 1 month ago

4048 Tracking it via the linked thread. Please provide full request and response in that thread.

johnkw commented 5 days ago

See also bug #4253 which notes the only current workaround is delete everything and retry.