ComfyUI Node: ⏪ Cycle Finish

⏪ Cycle Finish:

The CycleEnd node is designed to conclude a Cycle, a type of loop that iterates each time a prompt is executed. This node is essential for workflows that require iterative data processing, as it allows information to be passed forward into subsequent prompts. By connecting the CYCLE input of this node to a Cycle's CYCLE output, you establish a loop where data from Data and Aux Inputs flows through the CYCLE line and is cached for retrieval in the next iteration. The node outputs the current loop counter value and indicates whether the loop has finished based on the specified end value.

⏪ Cycle Finish Input Parameters:

CYCLE

The CYCLE input parameter is a dictionary that holds the state of the loop, including the current index, start, end, step, and other auxiliary data. This parameter is crucial for maintaining the loop's state across iterations. It must be connected to a Cycle node's CYCLE output to function correctly.

index_override

The index_override parameter allows you to manually set the loop counter to a specific value. This can be useful for debugging or for specific use cases where you need to control the loop index directly. If not provided, the loop will continue with its current index.

⏪ Cycle Finish Output Parameters:

index

The index output parameter returns the current value of the loop counter after the step is applied. This value is essential for tracking the progress of the loop and can be used in subsequent nodes to make decisions based on the current iteration.

finished

The finished output parameter returns a boolean value indicating whether the loop counter has reached or surpassed the specified end value. This is useful for determining when the loop has completed its iterations and can be used to trigger other actions or nodes in your workflow.

⏪ Cycle Finish Usage Tips:

• Ensure that the CYCLE input is correctly connected to a Cycle node's CYCLE output to establish a proper loop.
• Use the index_override parameter for debugging or specific scenarios where you need to control the loop index manually.
• Monitor the finished output to determine when the loop has completed and to trigger subsequent actions in your workflow.

⏪ Cycle Finish 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 to a Cycle node's CYCLE output.
• Solution: Ensure that the CYCLE input is correctly connected to the appropriate Cycle node's CYCLE output.

CYCLE [unique_id] START - DRY RUN

• Explanation: This message indicates that the loop is in its initial dry run phase, where the index, data, and auxiliary data are set to None.
• Solution: This is a normal part of the loop's initialization. No action is needed unless you want to handle the dry run phase differently in your workflow.

CYCLE [unique_id] AUTO-RESET!

• Explanation: This message indicates that the loop has automatically reset to the start value after completing its iterations.
• Solution: This is expected behavior if the auto-reset option is enabled. No action is needed unless you want to change the auto-reset setting.