Put your 16 strongest hooks first: Sume bulk queues start in order

Put your 16 strongest hooks first. A Sume bulk run dispatches items in the order you send them, and the 202 receipt already shows the first concurrency items running. With concurrency: 16 and 100 items, items 0 to 15 start at once, and the other 84 wait for slots.

The order is a free lever. If you have to stop early because of budget or a bad Format, the items that ran are the ones you ranked highest.

What the docs say

The bulk runs page says the server keeps concurrency child runs in flight, and starts the next queued item as soon as a slot opens. Create already fills the window. With concurrency: 3 and 8 items, the receipt shows three running and five queued.

There is no public cancel-queue endpoint. You can cancel a child with POST /v1/format-runs/{run_id}/cancel, which frees its slot for the next item.

How to use the order

Sort the spreadsheet before you build the body: strongest hook first, tests and long shots last. Item index is the zero-based position, so map results back to rows by index.

Workspace generation concurrency still applies to the children, so a window of 16 can run narrower than 16. A child that fails to start becomes failed with run_id: null, and the queue goes on.

Limits worth knowing

The queue accepts 1 to 100 items. A bad item fails the whole create with 400 and details.index before any queue exists, so validate the list first. Order does not change price: each child is billed on its own run.