Instagram Edits Manage versions vs Sume Format bulk runs

In the Edits app you keep several versions of one project through Manage versions. On Sume the closest workflow for variants is a Format bulk run: POST /v1/formats/{format_id}/bulk-runs queues 1 to 100 Format runs, keeps concurrency of them in flight, and you read each child run's result.

Edits facts are from the Instagram for Creators post, read 2026-10-01; Sume facts are from the Bulk runs docs. They are different tools: Edits is a phone editor, bulk runs are an API queue.

How does Edits handle versions?

The post says you can create multiple versions of a single project without cluttering the projects grid and switch between them. You tap the project name, then Manage versions, to add, rename or switch. It also says templates can lock clips, and a locked clip carries over for anyone who reuses the template.

How do bulk runs map to variants?

Each item in items is the same body as a single Format run, so a variant is one item with its own instruction or input. The create returns 202 with a queue id (frq_...); poll GET /v1/format-run-queues/{queue_id} for counts, and read each child at GET /v1/format-runs/{run_id}.

What does the Idempotency-Key do?

Send Idempotency-Key on create. The same key with the same { concurrency, items } returns 202 and the existing queue; the same key with a different payload returns 409 idempotency_conflict. Use a fresh key per batch, because replaying a spent key returns the old queue. See idempotency keys for AI video APIs.

What should I watch for?

Queue status completed means every item is terminal, not that all succeeded; check counts.failed and counts.canceled. Service-account keys cannot create Format runs or bulk queues. There is no cancel-queue endpoint; cancel a child with POST /v1/format-runs/{run_id}/cancel.