ComfyUI > Nodes > ComfyUI-cluster > Live Status

ComfyUI Node: Live Status

Class Name

LiveStatus

Category
Ollama/Debug
Author
GeekatplayStudio (Account age: 4275days)
Extension
ComfyUI-cluster
Latest Updated
2026-02-13
Github Stars
0.02K

How to Install ComfyUI-cluster

Install this extension via the ComfyUI Manager by searching for ComfyUI-cluster
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-cluster in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

Live Status Description

Real-time monitoring node emitting status messages for workflow progress tracking and user feedback.

Live Status:

The LiveStatus node is designed to facilitate real-time monitoring by emitting status text that can be displayed in the user interface. This node is particularly useful for tracking the progress of various stages in a workflow, providing immediate feedback to users. By emitting status messages, it helps in debugging and understanding the flow of operations, making it easier to identify where a process might be experiencing issues. The primary function of this node is to generate a formatted status message that combines a stage identifier with a descriptive message, which is then logged and returned for display purposes. This capability is essential for maintaining transparency and clarity in complex workflows, ensuring that users are always informed about the current state of their operations.

Live Status Input Parameters:

stage

The stage parameter is a string that represents the current phase or step in the workflow. It acts as an identifier for the status message, allowing users to quickly understand which part of the process is being referenced. This parameter is crucial for organizing and categorizing status updates, especially in workflows with multiple stages. The default value for this parameter is "stage", but it can be customized to reflect specific stages relevant to your workflow.

message

The message parameter is a string that contains the detailed description or information about the current status. This parameter supports multiline text, allowing for comprehensive messages that can include detailed explanations or instructions. The message is combined with the stage identifier to form a complete status update. By default, this parameter is an empty string, but it should be populated with relevant information to provide meaningful feedback to users.

Live Status Output Parameters:

status

The status output parameter is a string that represents the formatted status message generated by the node. It combines the stage and message input parameters into a single string, formatted as "[stage] message". This output is crucial for displaying the current status in the user interface, providing users with immediate feedback on the progress and state of their workflow. The status message helps in identifying the current stage and understanding any issues or updates that may arise during the process.

Live Status Usage Tips:

  • Customize the stage parameter to reflect meaningful identifiers for each step in your workflow, making it easier to track progress and identify issues.
  • Use the message parameter to provide detailed and informative descriptions of the current status, ensuring that users have a clear understanding of what is happening at each stage.
  • Regularly monitor the emitted status messages to quickly identify and address any potential issues in your workflow.

Live Status Common Errors and Solutions:

Error reading registry: <error_message>

  • Explanation: This error occurs when there is an issue reading the model registry file, possibly due to an incorrect file path or file permissions.
  • Solution: Ensure that the registry_path parameter is set to the correct path of the model registry file and that the file has the appropriate read permissions.

Status extraction failed: <error_message>

  • Explanation: This error indicates that there was a problem extracting the status from the response, which could be due to an unexpected response format or missing data.
  • Solution: Verify that the response format is as expected and that all necessary data is present. Check for any changes in the API or data source that might affect the response structure.

Live Status Related Nodes

Go back to the extension to check out more related nodes.
ComfyUI-cluster
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

Live Status