Salesforce Automation System · Rate Limits

Salesforce Automation System Rate Limits

Salesforce enforces consumption of its automation APIs through a per-org 24-hour API request allowance scaled by edition + license count, plus per-transaction Apex governor limits and concurrent-request ceilings. Exact per-edition allowance numbers were not retrievable in this run (Salesforce documentation pages bot-gated). This artifact captures the model and points to Salesforce's published limits cheatsheet.

4 Limits Throttle: 429
CRMAutomationSalesforceRate Limiting

Limits

Per-org 24-hour API request allowance org
requests_per_day
see Salesforce App Limits Cheatsheet (varies by edition + license count)
REST, Bulk, Streaming, and Tooling API calls share a single 24-hour bucket scaled by edition and license count.
Concurrent long-running synchronous requests org
concurrent_requests
see Salesforce App Limits Cheatsheet
Caps concurrent long-running (>20s) synchronous requests per org.
Apex governor limits transaction
varies
see Apex Developer Guide governor limits
Per-transaction limits on SOQL, DML, callouts, CPU time, and heap size apply to Flow / Apex automation.
Flow concurrency limits org
concurrent_flows
see Salesforce Flow limits documentation
Limits on concurrent flow interviews and scheduled flow runs are documented per release.

Policies

Edition + license scaling
24-hour allowance is computed as a per-edition base plus a per-license additive.
REQUEST_LIMIT_EXCEEDED
Returns 403 with REQUEST_LIMIT_EXCEEDED once the rolling 24-hour allowance is exhausted.
Bulk API for high-volume
Use Bulk API for large data movement to avoid burning the per-call REST allowance.
Apex transaction discipline
Per-transaction governor limits are hard. Bulkify SOQL / DML; avoid callout fan-out per record.

Sources