The terminology around batch processing limits is being refined to eliminate developer confusion. Previously, the phrasing left ambiguity about whether the platform limit restricted active job execution or just the initial processing of the triggers.
The and external are being updated to use the exact term "Batch trigger processing concurrency." The new descriptions state that this limit specifically controls the maximum number of batches being converted into individual runs simultaneously per environment. The text now explicitly notes that this is not a cap on how many batch runs can execute at once, making throughput modeling more predictable.