invalid_order_status — order is in the wrong status

An order-level refusal of bulk retry: POST /orders/{order}/items/retry-failed → 422 {"success": false, "message": "…", "reason": "invalid_order_status"}. No chunks were queued.

Bulk retry accepts an order only in the partially_completed status. completed and result_delivered have nothing to retry, failed / cancelled / compensated have no locked remainder left, and created / pending / in_progress are still being processed — there is no result yet.

Check the order status before calling. Neighboring refusals from the same endpoint differ by reason: 409 stitch_in_progress (the order is being stitched — wait and retry), 422 generative_not_supported (sfx/music: they have no single-chunk retry), 422 nothing_to_retry (no failed chunks were found).

GET /orders/{order} — the current status. If the order is already completed but you are not satisfied with the result, you need the order-level POST /orders/{order}/retry: it creates a NEW order with the same parameters and is billed again.

• Guide: the async model
• Guide: retries and idempotency
• POST /orders/{order}/items/retry-failed
• GET /orders/{order}
• POST /orders/{order}/retry