Hi @hellyars
Just to add a simple rule rule that you can use to determine whether to use an iterative or batch macro.
If you know the number of iterations before you start the macro AND the inputs don't change between iterations, use a Batch macro. Otherwise use an Iterative macro
In your case, you know the number of iterations (53) AND the Inputs don't change between iterations so a batch macro is the way to go with 53 records in the control parameter.
A typical use cases for an Iterative macro is calling an API that implements paging. Many of these return a result in the response that gives you the URL of the next page or an offset to add to a start value. When there are no more pages, the API doesn't return the next page result. You can't use a batch macro because you don't know how many pages are in the data until you call the first one.
The other typical iterative use case is where your building some kind of hierarchy of indeterminate depth. Here the inputs change between iterations, because you pass all the records in the first iteration and pull out the top level parents. For the next iteration you either remove the parent records from the input or mark them in some way so they are ignored. You keep on iterating until all the records are either removed from the input or marked.
As an aside, you can always convert a batch macro into an iterative one, by embedding the stop logic into it. In your case it would be stopping when engine.iteration number = number of pages - 1. I wouldn't recommend doing this though, since the logic because more complex and harder to maintain
Dan
