What it requires. A prompt template or agent action invoked inside a loop, once per record, where the platform offers a bulk or batched path.
Why it matters. Metered per action, the naive shape is expensive in a way that does not show up until the bill. At 20 Flex Credits an action, a per-record call across a 5,000-row job is a $500 line item where a batched design costs a fraction of it. Measured on the same shape, 109 evaluations through one batch took about 11.6 minutes rather than 36 times the duration of a single call, which is why batching is the remedy rather than an optimisation.
How to fix it. Move the call outside the loop and pass the collection, or use the platform's batched path.
Source. Salesforce Flex Credits pricing; our batch runner implementation
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.