409 — state conflict

The request was not executed because of a race: the server state changed between two of your calls. Nothing was created or charged.

Two cases. quote_mismatch on POST /orders and POST /orders/{order}/retry — the PAYG top-up quote is stale: a parallel order consumed quota, and the top-up got more expensive. stitch_in_progress on POST /orders/{order}/items/retry-failed — the result of the order is being stitched right now, and a bulk retry is not accepted at this moment.

Branch on reason. quote_mismatch is resolved with a new quote, not by repeating the old one; stitch_in_progress — by waiting a few seconds and repeating the same call. Both are safe to retry: a 409 arrives BEFORE any charge.

On quote_mismatch — the same POST /orders without confirm_payg_topup and without quote_token: the server returns a fresh 402 with the new price.

• quote_mismatch — quote is stale
• payg_topup_required — offer to top up
• Guide: LMC, quotas, and PAYG
• POST /orders