Retool concurrency 100, burst 200, and Sume bulk runs

Send one Sume bulk run instead of up to 100 separate workflow triggers. A bulk run takes 1 to 100 items and a concurrency of 1 to 16, so a single Retool workflow run can queue 100 renders while Sume limits how many are in flight, leaving your 100 concurrency and 200 burst numbers largely unused.

What do the Retool numbers mean?

On cloud, the Retool page says workflow concurrency is 100 and the burst limit is 200. Concurrency defines active runs within 15 minutes; the burst limit controls triggers within 10 seconds. Fanning out one workflow trigger per row spends both budgets quickly.

How should I size a Sume bulk call?

Put up to 100 entries in items, each the same body as a single Format run, and choose concurrency for how many child runs stay in flight. A bad item fails the create with 400 invalid_request and details.index before any queue exists. Mint a fresh Idempotency-Key per batch, since replaying a spent key returns 202 with the old queue. Details in Bulk runs; a worked example is Format bulk runs for 100 renders.

How do results get back to Retool?

The queue has no webhook; communication.webhook_url is per item, and queue-level progress comes from polling status_url. Per-item run webhooks retry up to 10 attempts, so dedupe on the envelope's request_id (the run id) in the Retool workflow that receives them; see Run webhooks. Each delivery is one trigger against your burst limit, so check that a 100-item batch finishing together stays under 200 triggers in 10 seconds.

Does completed mean everything succeeded?

No. completed means every item is terminal. Branch on counts.failed and handle failures separately.