Request rate, upload/storage quotas, commercial quotas and active conversion concurrency are separate controls. Treat them independently in capacity planning.
Different limits
HTTP abuse receives 429. Valid work that exceeds execution concurrency is normally accepted and queued rather than rejected. File-size and monthly-plan limits fail before expensive execution begins.
Concurrency queues
If your plan allows 10 active Tasks and you submit 1,000, ConverterHQ can run 10 and queue 990 while fair scheduling prevents one tenant from starving others. Monitor queue age as well as active count when tuning throughput.
Headers
Rate-limited surfaces expose standard limit/remaining/reset metadata and Retry-After where meaningful. Treat headers as live server guidance rather than hard-coding one global request rate into your SDK wrapper.
Client behavior
Bound client concurrency, add jitter to retry delays and apply backpressure before your own queues become unbounded. For bulk workloads, submit durable Jobs and allow ConverterHQ scheduling to absorb short bursts instead of opening thousands of synchronous waits.