The ‘Adjust Capacity during Bulk Transactions’ setting determines whether user load should be recalculated during bulk transactions, or only afterwards. This article dives deeper into its use cases, and pros and cons.
At each Match Group, at subtab ‘Settings’, you can enable or disable the ‘Adjust capacity during bulk transactions’ setting. Capacity, or user load, can be determined and calculated by use of Capacity Models. The ‘Adjust capacity during bulk transactions’ setting determines whether a user's capacity is recalculated during bulk transactions, while each record is processed, or only afterwards when such a transaction has finished.
Definition of ‘bulk transaction’
Note that a batch job in Salesforce can consist of many transactions, each processing a subset of records. “After a bulk transaction” means “after processing such a subset of records has finished”, not only after the entire batch job has finished.
Having the setting enabled
When ‘Adjust capacity during bulk transactions’ is enabled (real-time update), Assignee Capacity is updated immediately as records are processed.
This ensures that the capacity values are always up to date, and that capacity limits are enforced at the time of each assignment. By checking and decrementing capacity on a per-record basis, over-assignment is prevented.
However, this increases processing overhead during bulk transactions. Furthermore it raises the risk of hitting Salesforce governor limits (e.g. CPU time, DML limits) when processing large data volumes.
Recommendation
Enabling this setting is recommended in scenarios where accurate real-time capacity control is critical (for instance, to prevent overshooting capacity limits per Assignee). And in situations where the volume of transactions is manageable, so that real-time updates do not adversely affect performance.
Having the setting disabled
When ‘Adjust capacity during bulk transactions’ is disabled (deferred update), Assignee Capacity updates are postponed until the bulk transaction has completed.
This approach may temporarily lead to outdated capacity information during processing, with slight over-assignment as a result.
However, it can be more efficient in high-volume scenarios. It reduces the immediate processing load during bulk operations, plus it improves overall performance by batching capacity updates.
Recommendation
It is recommended not to use this setting in scenarios where performance is a concern, and a slight over- capacity is acceptable. Also disable the setting when system logs or testing indicate that real-time updates are causing governor limits to be reached.
