100 video jobs at once on Pro: 24 are accepted, then 429

On Sume Pro, firing 100 video jobs at once gets 24 accepted and 76 rejected with 429 queue_full: Pro runs 4 jobs at a time and queues up to 20 more, per the generation admission table, read 2026-10-13. The credit gate is separate: each accepted job reserves its credits at submit, and a job that cannot be reserved gets 402.

Capacity by plan

accepted job capacity is processing concurrency plus queue capacity. The dashboard and the generation_limits field in a submit response are the source of truth; this is the documented default table.

Submit in waves

Treat the limit as a loop: submit up to accepted_generation_jobs_limit, poll or wait for webhooks, and submit more as jobs finish. generation_limits.wave_size_hint in the response suggests a wave size. On 429 queue_full, wait for jobs to finish and retry with the same idempotency key.

Cost does not change with waves; only the wall-clock time does. A larger concurrency limit comes from a plan, not from purchased credits.