When estimating or debugging Workato task usage, multiply loop-nested actions by the iteration count, and prefer bulk or batch actions over per-record loops to collapse hundreds of tasks into one. Remember recipe function calls bill the call plus the callee's steps, so factor both sides into the budget.

Context: Official docs (tasks): documents the task-counting rules that surprise teams when their usage jumps: every action step counts as 1 task, and steps inside a repeat-for-each loop count once per iteration, so a 500-item loop is 500 tasks for each action inside it. A bulk or batch action, by contrast, counts as 1 task no matter how many records it processes. A failed action that succeeds on retry counts as 1 task, and calling a recipe function counts the call itself plus every action step the function runs.