One dead image URL fails the whole 100-item Sume bulk create

If one item in a 100-item bulk body has an attachment URL that Sume cannot fetch, the whole create fails and no queue is made. The API resolves every item's attachments before it creates the queue, so the failure shows up in seconds instead of minutes into a run.

Why it fails early

For a single run, Sume fetches each attachment at create, checks its real type and size, and copies it into durable storage. A broken or private image fails the create with a 4xx or 5xx you can act on, rather than stopping the run later. Bulk keeps that rule: the attachment codes are returned before the queue is created.

A pre-flight that costs nothing

Image types are JPEG, PNG, WebP, GIF and AVIF, up to 30 images and 30 MB each per run. Before you build the bulk body, check each URL yourself.

• Send a HEAD or a ranged GET from your own server with no credentials, since Sume fetches without auth.
• Drop or repair rows that fail, and keep a map from item index to SKU so you can report which row was dropped.
• Re-create with a new Idempotency-Key if you changed the body; the same key with a different payload is 409 idempotency_conflict.

Reading the failure

The error names the problem, not always the item, so keep the bulk body you sent and bisect if the response does not point at a row. Because nothing was dispatched, a retry after you fix the URL is clean: no children exist and nothing was charged.

If you send a changed body, give it a new Idempotency-Key. The same key with a different payload returns 409 idempotency_conflict and names the original queue in details.queue_id, which is only useful when a queue was created in the first place.

A practical habit is to store each product image on a host you control, so the URL cannot go stale between your pipeline run and the queue create. Check every URL before you send the body, because one bad item stops the whole create before any queue exists.

Tradeoff

Failing the whole create is strict, but it means a bad image never costs you a generation. The cost is that one stale CDN link can block 99 good rows until you remove it. A pre-flight pass is cheaper than finding out from a 502.