Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Job status

ComfyUI Node: OpenKatana · Job status

Class Name

OpenKatanaJob

Category
OpenKatana/Studio
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana 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

OpenKatana · Job status Description

Checks existing OpenKatana background job status without submitting or retrying work.

OpenKatana · Job status:

OpenKatanaJob lets you check an existing OpenKatana background job without submitting new work or retrying an earlier request. It is useful when a render or another background operation continues separately from your ComfyUI workflow and you want to find out whether it is still running, has finished, or needs attention. For local render jobs, the status-reading process checks saved job information, looks for a successful render receipt, and checks whether a recorded worker process is still alive. This helps you distinguish between work that is progressing and work that has stopped unexpectedly, without accidentally launching a duplicate operation. A returned tool result may itself contain a pending model receipt, so completion of a background tool job does not necessarily mean that every model operation associated with it has finished.

OpenKatana · Job status Input Parameters:

job_id

A required STRING identifying the existing background job you want to inspect. Use the identifier returned when that job was originally submitted; this is a job identifier, not a project name, video filename, or model receipt identifier. Changing it changes which job the node checks, but does not create, restart, or modify the selected job. The default is an empty string, "", which is only a placeholder and should be replaced with an actual job identifier before execution. The node interface specifies no minimum or maximum string length and provides no list of selectable options. The identifier must correspond to a job accessible in the OpenKatana environment handling the request; otherwise, the status lookup can fail.

OpenKatana · Job status Output Parameters:

result_json

A STRING containing the status tool’s response as JSON text. This is information about the job, not a directly usable image or video output. Read the returned state and any accompanying message to determine what happened, and parse the JSON if you want to use individual values elsewhere in your workflow. For the supplied local render implementation, the response includes saved job information and adds project and video_path as absolute filesystem paths; the presence of a video path alone does not prove that the video has finished rendering or exists yet. A running job with recorded process information can include pid, the worker process identifier, and rendered_frames, the number of PNG frame files currently found in the render folder. A successful render receipt adds state set to succeeded, frames, and sha256, a checksum used to identify the rendered result. If a running worker is confirmed to have stopped without a completed receipt, the state becomes interrupted and a message explains that the request is not automatically restarted. Failed local jobs can include diagnostic text from the last 3,000 characters of their log. Available fields depend on the job and the service handling the request; do not assume every response contains every field, and inspect any nested pending model receipt separately.

OpenKatana · Job status Usage Tips:

  • Copy the exact job identifier from the original submission result into job_id. Keep it with your project notes or workflow so you can inspect the same operation later without submitting it again.
  • Execute the node again when you need a fresh status snapshot. Its implementation makes one status request per execution; it does not contain an automatic polling loop or a configurable refresh interval.
  • For local renders, check state before treating video_path as a finished asset. Use succeeded as the success indication rather than assuming that a returned destination path means rendering is complete.
  • When available, compare rendered_frames across separate checks to see whether frame files are accumulating. This is a frame-file count, not a guaranteed completion percentage or an estimate of time remaining.
  • Inspect any pending model receipt contained in the returned tool result before assuming the underlying model work is finished. A background tool’s status and a model request’s status may represent different stages.
  • If the job reports failed or interrupted, read its diagnostic message before starting replacement work. OpenKatanaJob does not retry jobs, and repeated status checks will not restart a stopped worker.
  • There are no quality, resolution, speed, or retry settings on this node. Its only configuration selects the job to inspect; change rendering settings in the operation that submits the render, not here.

OpenKatana · Job status Common Errors and Solutions:

Missing or incorrect job identifier

  • Explanation: Leaving job_id at its empty default, using a project identifier instead, or entering an identifier for an unavailable job can prevent the status request from finding the intended record. The exact error wording depends on the service handling the request.
  • Solution: Copy the identifier from the original job-submission response, check for accidental spaces or missing characters, and confirm that you are checking the same OpenKatana environment where the job was submitted.

Job not found

  • Explanation: The supplied hosted job-store implementation raises this message when it cannot find a job matching both the requested identifier and the authenticated account. This is specific to that implementation, rather than a guaranteed message from every status request.
  • Solution: Verify the job identifier and use the account that submitted the job. If you switched accounts or service environments, return to the original one before checking again.

FileNotFoundError / No such file or directory

  • Explanation: The supplied local status reader opens saved job files, including job.json. If the relevant job folder or a required file is missing, a file-not-found error can occur. Possible causes include an incorrect identifier, deleted job data, or a project location that is no longer available.
  • Solution: Confirm the identifier and restore access to the original project storage. If job files were moved or deleted, restore them from a backup when possible; checking status cannot recreate missing job records.

Worker exited without a completed receipt; this request is not automatically restarted

  • Explanation: This exact message accompanies the local interrupted state when a job was marked as running but its recorded worker process is confirmed to have stopped without a successful completion receipt. It is a status diagnosis, not an instruction that an automatic retry is underway.
  • Solution: Inspect the job’s log.txt for the reason the worker stopped and address that problem before explicitly submitting replacement work through the appropriate submission tool. Re-running OpenKatanaJob only checks the status again.

Job state is failed

  • Explanation: The background operation encountered an error. The worker records exception information, and the local status reader replaces the failure message with the last 3,000 characters of log.txt when that file exists. The actual error text therefore depends on what failed during rendering or worker startup.
  • Solution: Read the returned message and, if necessary, the full log to identify the specific cause. Correct that issue before submitting another job; this status node cannot repair or retry the failed operation.

JSONDecodeError

  • Explanation: The local status reader parses saved JSON files such as job.json, process.json, and a render receipt when present. An incomplete or damaged file can cause a JSON parsing error instead of a normal status response; the precise message depends on the parsing failure.
  • Solution: If the job is actively writing files, try another status check shortly afterward. If the error persists, inspect the affected file and restore a valid copy from backup when available. Avoid manually changing the state to succeeded, because that does not complete or validate a render.

PermissionError / Permission denied

  • Explanation: The local status request needs permission to read the project’s job records and related files. Restricted access to the storage location can prevent it from reporting status.
  • Solution: Make sure the account running OpenKatana can read the project folder, job metadata, receipts, and logs. If the project is on an external or shared drive, confirm that the drive is connected and accessible.

OpenKatana · Job status Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
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.

OpenKatana · Job status