Hi @koryknick - Please find the below attached screenshots where both error at 64th iteration and also the iterations that have reached 99 is attached
second image has gone until 99th iteration…
@Noushin - let’s take a step back and make sure we are both using the correct terminology.
Recursion would be a pipeline that calls itself via Pipeline Execute - maximum depth is 64 calls deep in the stack of pipelines. Recursion is typically used to perform a task based on the current input value until a condition is met. For example, you may need to use recursion to get the full directory tree of a file system, so you get the listing of the current directory and then recursively call the pipeline for each directory to get the file list of each child directory. Recursion in Dashboard looks like this:
Iteration is calling a child pipeline by passing input documents in the stream to perform operations on each document. This is the typical (and recommended) pattern of calling the Pipeline Execute. Iteration in Dashboard looks like this:
Based on the error I see in your original thread, I believe you mean that previous executions only allowed 64 iterations (not recursion) and would indicate that something was consuming too many resources on the Snaplex node to allow any more child pipelines to execute. You may want to work with your SnapLogic CSM to look at your capacity planning. There is no limit to the number of child pipeline executions but you would lose visibility of the statistics after a number of iterations.
Hi @koryknick - Even I am making recursive calls using pipeline execute snap with condition until all records from the soap services are extracted i call same pipeline in recursive mode…And in the image i have dedelected the group pipelines checkbox hence its not on tree structure, please find the below image which depicts the recursive call.
