Timeout during order.create but the booking is still created

[godoyLeonardo]

Hello !

Today during a routinary audit we found that for at least a couple of flights, we had this problem where the call to ORDER (we assume order.Create) has timed out but the booking has been successfully created in Duffel.

Could you help us find a solution?

What we have come up with so far:

• Increase the timeout in the SDK (how?)
• If the endpoint fails, try again in another way (how? This endpoint is the one that returns the success and the booking reference, calling the same endpoint again would create a duplicate booking. And if we don't call the endpoint again, how would we know that the booking had already been created if we don't have the reference to check?).

Thank you

[igorp1]

Hi @godoyLeonardo, thank you for flagging this.

There isn’t currently any timeout parameter you can pass to the SDK or API request to extend how long it waits. So it isn’t something we can configure on the Duffel side.

If a request times out client-side, the order may still be created on our side, which is why retrying order.create can risk duplicates.

This is more of a product/workflow question than an SDK one, so I’d recommend contacting help@duffel.com with the affected details and timestamps so the team can investigate and advise.

[godoyLeonardo]

Hello @igorp1

Quick question, what's the timeout configuration for the calls made through the SDK? How long the SDK waits before throwing an error or empty response?