Salesforce Automation · Rate Limits
Salesforce Automation Rate Limits
Salesforce enforces API consumption through a per-org 24-hour API request allowance that scales with the org's edition and 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.
3 Limits
Throttle: 429
CRMAutomationB2BRate Limiting
Limits
Per-org 24-hour API request allowance org
see Salesforce App Limits Cheatsheet (varies by edition + license count)
Salesforce sums REST, Bulk, Streaming, and Tooling API calls into a single 24-hour bucket scaled by edition and the number of licenses in the org.
Concurrent long-running synchronous requests org
see Salesforce App Limits Cheatsheet
Salesforce caps concurrent long-running (>20 sec) synchronous requests per org.
Apex governor limits transaction
see Apex Developer Guide governor limits
Per-transaction limits on SOQL queries, DML rows, callouts, CPU time, and heap size apply to automation flows.
Policies
Edition + license scaling
The 24-hour API allowance is computed as a per-edition base plus a per-license additive, so allowance grows with the org's license count.
REQUEST_LIMIT_EXCEEDED
When the daily allowance is exhausted, Salesforce returns 403 with REQUEST_LIMIT_EXCEEDED. Clients must wait until the rolling 24-hour window allows new traffic.
Bulk API for high-volume
For data loading, Salesforce expects clients to use Bulk API rather than burning REST allowance, since Bulk batches consume fewer of the daily call buckets relative to records processed.
Apex transaction discipline
Per-transaction governor limits are hard. Automations should bulkify SOQL / DML and avoid callout fan-out that would breach per-transaction caps.