-
Notifications
You must be signed in to change notification settings - Fork 2
Looper Node
A powerful node for iterative processing of data with configurable loop behavior. Enables iterative operations by managing internal input and output connections, making it ideal for tasks that require repeated processing or accumulation of results. Functions similarly to a sophisticated 'for' loop while maintaining node graph connectivity.
Starting value for the loop iteration. Must be non-negative.
Ending value for the loop iteration. Must be non-negative.
Increment value between iterations. Cannot be zero. Can be negative for reverse iteration.
When enabled, sets max iterations based on input data length.
Enables feedback loop mode where each iteration's output feeds into the next.
When enabled, runs only a single test iteration.
Specific iteration to run when use_test is enabled. Must be between min and max.
Controls whether to force cook operations on each loop iteration.
Custom input processing hook (advanced usage).
Custom output processing hook (advanced usage).
Maximum execution time in seconds. Default: 300.0
Maximum memory usage in bytes. Default: 200MB
- Iterates from min to max by step
- Each iteration processes fresh input data
- Example: Processing a series of numbered files or generating sequences
- Activated with
max_from_input=True - Number of iterations matches input data length
- Ideal for processing lists or arrays item by item
- Example: Processing each item in a list with complex operations
- Activated with
feedback_mode=True - Output of each iteration becomes input for the next
- Useful for recursive or cumulative operations
- Example: Iterative refinement or accumulation of results
- Activated with
use_test=True - Runs single iteration specified by
test_number - Useful for debugging and development
- Example: Testing specific iteration behavior without running full loop
- Timeout protection via
timeout_limit - Memory usage limits via
data_limit - Automatic cleanup of stale loops
- Parameter validation to prevent invalid configurations
The node operates using two internal nodes:
- inputNullNode: Handles input data for each iteration
- outputNullNode: Collects and manages output from each iteration
- Iterations stop if
timeout_limitis reached - Warns if iterations produce null/blank values
- Last valid output is preserved in staging_data
- All iterations must process List[str] data types
min=1, max=10, step=1
# Result: Processes 10 iterationsmax_from_input=True
# Result: Iterations match input data lengthfeedback_mode=True
# Result: Each iteration processes previous iteration's outputuse_test=True, test_number=5
# Result: Only processes iteration #5