ComfyUI Node: RunningHub Workflow Executor

RunningHub Workflow Executor:

The RunningHubWorkflowExecutor node is designed to facilitate the execution and monitoring of workflows within the RunningHub platform. This node serves as a bridge between your creative processes and the automated capabilities of RunningHub, allowing you to initiate workflows and track their progress seamlessly. By leveraging this node, you can automate complex tasks, ensuring that they are executed efficiently and reliably. The node's primary function is to execute a specified workflow using an API key and workflow ID, then continuously monitor the task status until completion. This capability is particularly beneficial for AI artists who wish to streamline their workflow processes, reduce manual intervention, and focus more on the creative aspects of their projects.

RunningHub Workflow Executor Input Parameters:

api_key

The api_key is a string parameter that serves as a security credential, allowing the node to authenticate and interact with the RunningHub API. It is essential for ensuring that only authorized users can execute workflows. The default value is an empty string, and it must be provided for the node to function correctly.

workflow_id

The workflow_id is a string parameter that uniquely identifies the workflow you wish to execute. This ID is crucial for directing the node to the correct workflow within RunningHub. The default value is an empty string, and it must be specified to initiate the workflow execution.

node_info_list

The node_info_list is a parameter that contains a list of node information required for the workflow execution. This list provides the necessary context and configuration for the workflow, ensuring that it runs with the correct settings and data.

seed

The seed is an integer parameter used to initialize random number generation within the workflow. It ensures reproducibility of results by providing a consistent starting point for any stochastic processes. The default value is 0, with a minimum of 0 and a maximum of 0xffffffffffffffff.

max_attempts

The max_attempts is an integer parameter that defines the maximum number of attempts the node will make to check the task status. This parameter helps manage the node's persistence in monitoring the workflow, with a default value of 60, a minimum of 1, and a maximum of 1000.

interval_seconds

The interval_seconds is a float parameter that specifies the time interval, in seconds, between each attempt to check the task status. This parameter controls the frequency of status checks, balancing responsiveness with resource usage. The default value is 5.0 seconds, with a minimum of 1.0 and a maximum of 60.0.

RunningHub Workflow Executor Output Parameters:

file_urls

The file_urls output provides a list of URLs pointing to the files generated by the workflow. This output is essential for accessing and utilizing the results of the executed workflow.

task_id

The task_id is a string output that represents the unique identifier of the task created by the workflow execution. It is crucial for tracking and referencing the specific task within RunningHub.

msg

The msg output is a string that contains messages or notifications related to the workflow execution. It provides insights into the process, including any important information or alerts.

promptTips

The promptTips output is a string that offers suggestions or tips related to the workflow execution. This output can guide users in optimizing their workflow or understanding the results better.

taskStatus

The taskStatus output is a string that indicates the current status of the task, such as SUCCEDD, FAILED, QUEUED, or RUNNING. It is vital for understanding the progress and outcome of the workflow.

fileType

The fileType output is a string that specifies the type of files generated by the workflow. This information is useful for determining how to handle or process the output files.

code

The code output is a string that may contain any relevant codes or identifiers associated with the workflow execution. It can be used for further analysis or integration with other systems.

json

The json output is a string that provides a JSON representation of the workflow results or status. This output is valuable for programmatic access and further processing of the workflow data.

RunningHub Workflow Executor Usage Tips:

• Ensure that your api_key and workflow_id are correctly set to avoid authentication errors and ensure the correct workflow is executed.
• Adjust the max_attempts and interval_seconds parameters to balance between timely status updates and resource consumption, especially for long-running workflows.
• Utilize the seed parameter to achieve consistent results in workflows that involve random processes, which is particularly useful for testing and debugging.

RunningHub Workflow Executor Common Errors and Solutions:

Invalid response from workflow execution

• Explanation: This error occurs when the response from the workflow execution does not contain the expected data.
• Solution: Verify that the api_key and workflow_id are correct and that the RunningHub service is operational.

No task ID returned from workflow execution

• Explanation: The workflow execution did not return a task ID, which is necessary for monitoring the task.
• Solution: Check the workflow configuration and ensure that it is set up correctly in RunningHub.

Error checking task status

• Explanation: An error occurred while attempting to check the status of the task, possibly due to network issues or incorrect parameters.
• Solution: Ensure that your network connection is stable and that the api_key and task_id are valid. Retry the operation after a short delay.