ComfyUI Node: ⏩ Cycle Continue

⏩ Cycle Continue:

The CycleContinue node is designed to facilitate the continuation of a Cycle, a type of loop that iterates each time a prompt is executed. This node allows you to send information forward into subsequent prompts, enabling workflows that process data iteratively. By connecting the Data and Aux outputs of this node to a Cycle End node's Data and Aux inputs, you can continue the loop after processing the data. The Index output specifies the current value of the loop counter before the Step is applied. This node is particularly useful for propagating data into subsequent prompt executions, allowing for iterative data processing by queuing multiple prompts at a time or setting the execution to Instant, which queues up prompts automatically. Execution can be interrupted via the HaltExecution node once your Cycle has finished or for any other reason.

⏩ Cycle Continue Input Parameters:

CYCLE

The CYCLE input parameter is a dictionary that holds the state of the current cycle, including the loop index and any auxiliary data. This parameter is essential for maintaining the continuity of the loop and ensuring that the data is correctly propagated to subsequent iterations. There are no specific minimum, maximum, or default values for this parameter as it is dynamically managed by the cycle's state.

index_override

The index_override input parameter allows you to manually set the current value of the loop counter. This can be useful if you need to jump to a specific iteration within the loop. If not provided, the loop will continue with the current index value. This parameter is optional and does not have predefined minimum, maximum, or default values.

data

The data input parameter is used to pass any data that needs to be processed in the current iteration of the loop. This data will be propagated to the next iteration via the Cycle End node. There are no specific constraints on the type or format of the data, making it flexible for various use cases.

aux

The aux input parameter is used to pass auxiliary data that may be needed for processing in the current iteration of the loop. Similar to the data parameter, this auxiliary data will be propagated to the next iteration. There are no specific constraints on the type or format of the auxiliary data.

⏩ Cycle Continue Output Parameters:

index

The index output parameter specifies the current value of the loop counter before the Step is applied. This value is crucial for tracking the progress of the loop and can be used to make decisions based on the current iteration.

next

The next output parameter contains the data that will be passed to the next iteration of the loop. This allows for the iterative processing of data, enabling complex workflows that require multiple steps of data transformation.

aux

The aux output parameter contains the auxiliary data that will be passed to the next iteration of the loop. This is useful for carrying additional information that may be needed for processing in subsequent iterations.

⏩ Cycle Continue Usage Tips:

• Ensure that the CYCLE input is correctly connected to maintain the continuity of the loop and avoid errors.
• Use the index_override parameter to jump to specific iterations if needed, which can be useful for debugging or specific workflow requirements.
• Connect the data and aux inputs to relevant nodes to propagate necessary information into subsequent iterations, enabling complex data processing workflows.

⏩ Cycle Continue Common Errors and Solutions:

CYCLE [unique_id] NOT PROPERLY CLOSED. PLEASE CONNECT THE CYCLE NODES CORRECTLY!

• Explanation: This error occurs when the CYCLE input is not properly connected, disrupting the continuity of the loop.
• Solution: Ensure that the CYCLE input is correctly connected to the corresponding Cycle or Cycle End node to maintain the loop's state.

CYCLE [unique_id] START - DRY RUN

• Explanation: This message indicates that the loop is in its initial 'DRY RUN' state, where the Index, Data, and Aux_Data inputs are set to None.
• Solution: Use this state to reset any variables or the state of your workflow. Ensure that the Cycle node's parameters are correctly set to transition out of the 'DRY RUN' state.

CYCLE [unique_id] AUTO-RESET!

• Explanation: This message indicates that the loop has automatically reset to the original start value after completing a cycle.
• Solution: If auto-reset behavior is not desired, ensure that the auto_reset parameter in the Cycle node is set to False.