Sync Labs concurrent jobs per plan vs Sume plan-only concurrency

On Sync Labs the plan sets how many jobs run at once: Hobbyist 1, Creator 3, Growth 6 (Scale lists 15), and a new generation fails with 429 when you are at the limit. On Sume, generation concurrency is plan-only too, but a submit over the limit is normally accepted as queued and dispatched later; prepaid top-ups do not raise the limit.

Sync facts are from its pricing page and rate-limit guide; Sume facts from Generation admission, read 2026-10-01.

What does each Sync Labs plan allow?

What happens at the limit on Sync Labs?

The guide says you already have the maximum number of generations in PENDING or PROCESSING, so wait for one to finish or upgrade. It also says enterprise and contracted accounts may have custom limits that you should use instead of hardcoding the public table.

What happens at the limit on Sume?

Concurrency is a dispatch limit, not a submit limit. Jobs wait as queued while queue capacity remains; when the queue is full, new paid submissions fail with 429 queue_full. Queue capacity defaults to max(3, concurrency_limit × 5). Admin overrides can raise the effective limit, but top-ups cannot.

Where do I read my real limit?

The docs say the dashboard Concurrency tab and the generation_limits.concurrency_limit field are the source of truth, and that the static plan table in the docs is secondary. For a related comparison, see ElevenLabs concurrency vs Sume.