confirmTransportationOptions: Fail to execute CONFIRM_CARRIERS API with errors

[jlevers]

I'm integrating with the new FBA Inbound API v2024-03-20 for a client. The end-to-end flow was working, but at some point it started failing at the confirmTransportationOptions step with the error Fail to execute CONFIRM_CARRIERS API with errors, and no additional details on what's going wrong. Here's the full error payload:

{
    "operationStatus": "FAILED",
    "operationId": "c2fbebab-xxxx-xxxx-xxxx-1818a3cba30d",
    "operation": "confirmTransportationOptions",
    "operationProblems": [
        {
            "severity": "ERROR",
            "code": "BadRequest",
            "message": "ERROR: Fail to execute CONFIRM_CARRIERS API with errors."
        }
    ]
}

Per @johnkw's comment on #4184 that says these calls fail randomly some percentage of the time with the exact same inputs, I tried automatically retrying the call up to 20 times in a row with the same inputs, but got the same exact error every time. Again, this exact code with the exact values I'm using was working at one point, but now I'm getting this error. This behavior seems to be consistent with what others are seeing from the new FBA Inbound API.

I've had an open support case on Seller Central related to this issue for going on 2 weeks with no real responses beyond "we'll get back to you."

At one point, I was getting the ERROR: Something went wrong. Please try again later. error as well, but that seems to have vanished and has been replaced with the Fail to execute CONFIRM_CARRIERS API with errors issue.

If anyone has any insight into how to get past this problem, that would be much appreciated.

[johnkw]

The retries only worked with bug #4184. We also hit ERROR: Fail to execute CONFIRM_CARRIERS API with errors. and there was no way to recover from it within the workflow -- just stuck with the same error every time (12 hours later even). I deleted the workflow, and recreated everything with the same options a second time and it worked then.

[MeenaAmz]

@jlevers Can you please share the support case that you opened for the issue?

Thanks
Meena
Selling Partner Developer Services

[jlevers]

The retries only worked with bug #4184. We also hit ERROR: Fail to execute CONFIRM_CARRIERS API with errors. and there was no way to recover from it within the workflow -- just stuck with the same error ever time (12 hours later even). I deleted the workflow, and recreated everything with the same options a second time and it worked then.

Interesting, I've retried with the same options several dozen times, with no success. But I'm 100% sure the exact same code and inputs was working a couple weeks ago. It's reassuring to hear that I'm not the only one getting inconsistent results from this endpoint.

@jlevers Can you please share the support case that you opened for the issue?

Thanks Meena Selling Partner Developer Services

I have two – the more recent one is 16523362621, the other is 16429109411

[lightningja]

@jlevers I'm facing the same issue here. Always got ERROR: Fail to execute CONFIRM_CARRIERS API. Were you able to call the api successfully or it is failing all the time lately?

[jlevers]

Failing all the time – it worked a couple weeks ago, but since I started getting this error, I've never been able to make a successful call again.

[MeenaAmz]

The retries only worked with bug #4184. We also hit ERROR: Fail to execute CONFIRM_CARRIERS API with errors. and there was no way to recover from it within the workflow -- just stuck with the same error ever time (12 hours later even). I deleted the workflow, and recreated everything with the same options a second time and it worked then.

Interesting, I've retried with the same options several dozen times, with no success. But I'm 100% sure the exact same code and inputs was working a couple weeks ago. It's reassuring to hear that I'm not the only one getting inconsistent results from this endpoint.

@jlevers Can you please share the support case that you opened for the issue?
Thanks Meena Selling Partner Developer Services

I have two – the more recent one is 16523362621, the other is 16429109411

Thanks for providing the ids. We are investigating the issue further based on the information provided. Please follow the support case for further updates.

Thanks
Meena
Selling Partner Developer Services

[lightningja]

@MeenaAmz @jlevers I would really appreciate it if you guys could share the investigation results here!

[jlevers]

I'll definitely update the thread when I get any response – I just got a notification that my two cases were being combined into one, but no further information.

[xyloneX]

I have been constantly reporting this error, which is causing me great distress

[MeenaAmz]

@lightningja @xyloneX Have you created support cases as well? Can you please share the numbers if you did?

Thanks
Meena
Selling Partner Developer Services

[lightningja]

@MeenaAmz yes I just created a support case today. It is: 16558452781

Thanks!

[AshwinPitroda]

I’ve been facing this error frequently recently. It seems that, for the same payload, sometimes it works fine, while other times it fails to execute the CONFIRM_CARRIERS API with errors.

Does anyone have a resolution for this?

[johnkw]

The only resolution is to delete the entire Workflow (which includes deleting the pending Shipments) and recreate it identically, and hope it works. The error doesn't have anything to do with the inputs.