Platform limits and quotas, with sources

Anything a platform will refuse or throttle: rate limits and daily quotas, execution time caps, size and count limits such as cells per spreadsheet or attachment size, and plan-specific ceilings. Each row quotes the documented value, names the plan or edition it applies to, and links the official page it came from.

Limits often depend on the plan, edition, account age or region, and some are enforced per user while others are per project or per domain. These pages give each documented value with the plan it belongs to. If your provider or admin sets a lower ceiling, the lower one is the one that applies to you.

Every page shows the date its values were last checked against the official documentation. Vendors do change quotas, sometimes without announcement, so treat that date as part of the data and open the linked source before you rely on a number for a contract, a budget or a launch.

It depends on the kind of limit. Rate limits usually return a retryable error such as HTTP 429 and clear after a wait. Daily quotas reset on a schedule, often 24 hours after the first call. Size and count limits return a validation error that retrying never fixes. Each page describes the literal message and how long it lasts.

Sometimes. Some vendors raise quotas on a paid plan or on request through their console; others are fixed for everyone. The workaround sections on each page list only legitimate options: spreading the work out, batching requests, moving to a plan with a higher documented ceiling, or using the vendor's bulk API. Evading a platform's rules is never one of them.

Yes. A platform's limits apply to every client that calls it, Autonoly included. What a workflow adds is control over pacing: runs on a schedule or a trigger, retries with timeouts on each step, and error branches when a call is refused. Autonoly also has limits of its own, which the pricing page lists.