Free tools Windows power users keep installed
One-click scans. No signup required.
Before increasing CRM workflow volume, check your plan and account-wide quotas, measure the work each event triggers, and review concurrency, queues, and downstream API or connector limits. Then confirm that logs and alerts will still expose failures at the new volume. Raise capacity in measured steps and validate results against your actual workload: no single setting or safe increase applies across Salesforce, HubSpot, and Power Automate.
What should you check before raising workflow volume?
Start with a baseline of the automations affected and the work they perform. A higher event count can mean more database queries and writes, more connector requests, more retries, or more logs—not just more workflow runs. Identify peak arrivals as well as daily totals, and note run duration, actions per event, and which system owns each limit.
As an Amazon Associate I earn from qualifying purchases.
- Inventory the workload: list the affected workflows, their triggers, expected peak and daily events, actions per event, average run time, retries, and connected services.
- Confirm entitlement: check the plan or license associated with each automation and its active-workflow, daily-action, scheduled-run, or other applicable allocation.
- Inspect the work per event: look for repeated queries or writes, excessive connector calls, and actions that could be grouped or processed asynchronously.
- Review concurrency and backlog: record current parallelism, queue behavior, arrival bursts, and whether downstream systems can absorb the added requests.
- Check shared capacity and visibility: budget API and connector usage across integrations, and verify that execution logs, error alerts, and usage views will remain useful.
- Increase in controlled steps: compare completions, errors, retries, backlog, latency, and data integrity after each change. The vendor limits below are ceilings or allocations, not guarantees that a particular workload will meet its timing needs.
Which platform limits are useful reference points?
These documented figures illustrate why the right setting depends on the platform and automation type. They are not interchangeable and should not be treated as recommended targets. Confirm current documentation and the limits that apply to your account before changing production settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Platform and area | Documented reference | What it means for a volume increase |
|---|---|---|
| Salesforce Flow transaction limits | Salesforce Help lists 100 SOQL queries, 50,000 queried records, 150 DML statements, 10,000 DML-processed records, and 10,000 milliseconds of server CPU per transaction. The page’s publication year is not stated; accessed October 4, 2026. | These are per-transaction governor limits, not org-wide throughput targets. Exceeding them can roll back a transaction. |
| Salesforce Marketing Cloud flow bulk behavior | Salesforce describes grouping up to 200 record changes per transaction for certain named Marketing Cloud flow types. The page’s publication year is not stated; accessed October 4, 2026. | This scope applies only to those flow types; it is not a universal Salesforce batch size. |
| HubSpot workflow logs | HubSpot documents a cap of 100,000 successful execution logs per day, calculated from midnight in the account time zone, plus 90-day workflow action-log retention and six months of enrollment history. The page’s publication year is not stated; accessed October 4, 2026. | The daily cap is a logging limit, not necessarily an execution limit. After the success and info logging cap is reached, error logs continue to appear. |
| Power Automate trigger concurrency | Microsoft Learn documents a configurable range of 1–100 concurrent runs when concurrency control is enabled, with a default of 25. The page was updated September 22, 2026. | Concurrency control is off by default. When enabled, the documented waiting-run limit is 10 plus the configured degree of parallelism; a full waiting-run limit can affect later triggers. |
| Power Automate single-flow burst limit | Microsoft Learn documents a cap of 100,000 actions in five minutes for a single flow version. The page was updated September 22, 2026. | This is a burst cap, not a promise that connectors or Dataverse will accept requests at that rate. |
Does your plan or license provide enough capacity?
Check the entitlement attached to the automation, not just the CRM subscription name. Limits can depend on plan, edition, automation type, or flow owner. Separate active-workflow allocations and scheduled-run limits from execution throughput, daily actions, API allowances, and log retention; each describes a different capacity layer.
#1 Best Overall
- Salesforce: Flow limits are edition-specific. Salesforce also documents org-level Flow and scheduled-interview limits; scheduled-triggered interviews use a daily limit with an alternative license-based formula. A maximum allocation does not establish that a workload will finish within its latency target.
- HubSpot: Workflow counts vary by subscription. Customized workflows created in the workflows tool count toward the documented limits, while several embedded automations do not. Confirm which category each affected automation belongs to.
- Power Automate: The flow owner’s plan determines its performance profile. Microsoft documents action entitlement for a Process license and license stacking for certain flows. Those entitlements do not remove connector-specific or Dataverse service protection limits.
Should you increase concurrency or change queue behavior?
Parallel runs may improve throughput when work is independent and downstream services have headroom. They can also send a burst of requests into a connector or data service, creating throttling, failed runs, or a growing backlog. Decide based on measured run duration and arrival patterns, not on the assumption that more parallelism is always faster.
For Power Automate specifically, concurrency control is off by default. When enabled, Microsoft documents the range and queue behavior in the table above. Microsoft cautions that triggers arriving after the waiting-run limit is met might be retried by the connector; retries might not succeed if the limit remains full. Salesforce Flow and HubSpot do not inherit Power Automate’s numeric settings.
- Check connector and Dataverse capacity before raising parallel runs.
- Determine what happens to delayed, retried, or duplicate events, and make sure processing is safe to repeat where applicable.
- Test representative peaks and verify completed work, errors, queue depth, and record integrity before widening the rollout.
Is the work per transaction or event efficient?
More workflow volume magnifies inefficient automation. For Salesforce Flow, inspect queries, retrieved records, DML statements, records written, and CPU consumed in each transaction against the Salesforce limits in the table. Salesforce warns that exceeding governor limits can roll back the transaction even if a flow element has a fault connector path.
Review loops for queries or writes repeated once per record. Where the automation permits it, group related work rather than issuing the same operation repeatedly. Salesforce documents bulkification for certain named Marketing Cloud flow types; do not assume that behavior or its stated batch size applies to other flows.
For large imports or integrations, consider whether a bulk or asynchronous API is more appropriate than many synchronous requests. Salesforce Bulk API 2.0 has its own limits, and API capacity still needs to be budgeted alongside other integrations.
How much API and connector capacity will the new workload use?
Estimate requests and actions from expected event volume, work per event, retries, and connected applications. Include existing integration traffic: a CRM’s API allowance may be shared across the organization, while each external connector or service can enforce a separate rate limit.
- Salesforce: API calls are aggregated across org calls. Monitor Setup API usage views, API response headers, the
/limitsendpoint, and API usage notifications. Salesforce says occasional over-limit processing may be allowed for eligible paid orgs, but it is restricted and should not be relied on continuously. - Power Automate connectors: Each connector service can have its own throttling limit; throttling may return HTTP 429. Microsoft guidance says spreading requests over time, batching, or using an appropriate alternative connection may help with connector-level throttling.
- Dataverse: Service protection limits are separate from connector limits. A Process license does not raise Dataverse service protection limits, so additional license entitlement alone is not evidence that the data service can sustain the new rate.
Verify the current limits for the specific connector and integration. Do not equate a daily action entitlement with permission to send requests at any desired rate.
Will logs and alerts still reveal failures?
Before increasing volume, confirm that your team can see run counts, errors, retries, completion times, and queue or throttling signals. Keep a baseline and assign an owner to respond when errors rise or expected work remains incomplete. A quota dashboard alone cannot show that each record was processed correctly.
HubSpot’s documented logging cap and retention periods are listed in the table. Because the cap applies to successful execution logs, it can limit the success history available for investigation without stopping workflow execution; error logs continue after the success and info cap is reached. Salesforce’s API usage views and notifications show aggregate request consumption, so pair them with automation error monitoring and integration-side telemetry.
How should you choose which setting to change?
Identify the bottleneck before changing a control. Compare candidate changes across these dimensions:
- Capacity layer: Is the constraint a plan entitlement, org-wide allocation, transaction limit, connector quota, or data-service protection limit?
- Work shape: What are the peak arrivals, actions per event, run duration, batchability, and retry rate?
- Parallelism and reliability: Would more simultaneous work outpace downstream capacity, fill a queue, or increase delayed and repeated events?
- Observability: Will run, error, API-usage, and backlog evidence remain available long enough to diagnose problems at target volume?
- Ownership and cost: Which account or license funds the work, and who owns alerts, investigation, and remediation?
There is no universal safe percentage increase or concurrency value across CRM platforms. Use your account’s current usage and a representative workload to make a controlled change, then pause or roll back if failures, throttling, data discrepancies, or unresolved backlog rise.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
