OpenKatana · Get render:
OpenKatana_get_render provides a ComfyUI interface to OpenKatana’s render-related tool, allowing you to make a project-specific request from a node-based workflow rather than calling the tool directly in code. It prepares the request, sends it through OpenKatana’s tool-calling system, and returns the tool’s response for inspection or further processing. This is useful when you want to keep access to rendering information within your existing creative workflow. The supplied code confirms the request-and-response mechanism but does not include the underlying get_render implementation, so it does not establish whether this tool retrieves render status, render metadata, completed render files, or another render record. OpenKatana’s accompanying renderer code shows support for numbered PNG frames and rendering records, but those capabilities should not be interpreted as a guarantee that this particular node starts rendering or loads images into ComfyUI.
OpenKatana · Get render Input Parameters:
project_id
A required STRING that supplies the project context when the node prepares its OpenKatana tool request. Use the identifier associated with the project whose render-related information you want to access; this value is passed into the request-preparation helper together with the selected tool and the argument text. Providing the correct project context helps ensure that the request addresses the intended project, although the supplied code does not reveal the identifier format, project lookup rules, or how conflicts with values inside the argument text are handled. No default value, minimum or maximum string length, or list of accepted options is specified in the provided interface.
arguments
A required STRING containing the argument text used to construct the get_render request. The node passes this text through its argument-preparation helpers before invoking the tool, so its contents affect what is requested from OpenKatana. The supplied code does not show the accepted text format, the get_render argument schema, or any required keys; consequently, a specific JSON example or a render-identifier field cannot be documented reliably from this context alone. Use the argument format documented by your installed OpenKatana tool definition rather than adding guessed settings such as frame count, resolution, or frame rate. No default value, minimum or maximum string length, or enumerated options is shown.
after
An optional STRING accepted by the execution method, with a Python default of None when omitted. In the supplied implementation, this value is not read, added to the prepared arguments, or passed to the tool invocation. Therefore, the shown code provides no basis for treating it as a render filter, a timestamp, or an instruction to wait for another task to complete. Leave it unset unless your surrounding workflow or additional OpenKatana documentation gives it a specific purpose. No minimum or maximum string length, selectable options, or explicit interface-level text default is provided.
OpenKatana · Get render Output Parameters:
result_json
A STRING containing the response produced after the OpenKatana tool is invoked and its result is passed through the response-formatting helper. This is the node’s only output, so it should be treated as textual tool-response data rather than as a ComfyUI IMAGE, video, or frame batch. Its name indicates JSON-oriented output, but the supplied context does not include the response formatter or get_render response schema, so exact fields, success indicators, file paths, and error-envelope structure cannot be guaranteed. Inspect the returned text before building downstream processing around it; if it contains valid JSON, a suitable JSON-processing node can extract the fields actually present. Render manifests and receipts shown elsewhere in the context illustrate OpenKatana’s rendering records, but they are not a confirmed schema for this output.
OpenKatana · Get render Usage Tips:
- Confirm the get_render argument schema in your installed OpenKatana documentation or tool definition before configuring
arguments. The provided interface does not expose the tool-specific fields, so guessing their names can produce invalid requests. - Use the project identifier supplied by your project-management workflow. Do not substitute a project title or filesystem path unless your OpenKatana installation explicitly supports that format.
- Start with the smallest valid request supported by get_render and inspect
result_jsonin a text-display node. Once you know the actual response structure, connect downstream processing to the specific fields you need. - Do not expect this node to output visible images directly. If the returned response identifies rendered files, use an appropriate file or image-loading node to bring those assets into your visual workflow.
- Leave
afterunset unless you have a documented reason to connect it. The supplied execution method does not use its value to control the request or wait for rendering. - Configure rendering quality, dimensions, frame count, and frame rate in the appropriate rendering or project settings, not as additional inputs on this node. None of those controls is exposed by the authoritative interface.
- When troubleshooting, distinguish a tool-request failure from an underlying renderer failure. Request failures concern project context or argument construction; renderer failures concern the scene, page, hooks, or assets being rendered.
OpenKatana · Get render Common Errors and Solutions:
unexpected inputs: …
- Explanation: This is an explicit error in the supplied node wrapper. It is raised when extra execution fields are supplied that are not part of the tool’s allowed typed inputs. The authoritative interface exposes only
project_id,arguments, and optionalafter. - Solution: Remove additional node-level fields. If you need a tool-specific setting, first verify that get_render supports it and then supply it through the documented argument format rather than inventing another input.
Missing required input: project_id or arguments
- Explanation: This is a descriptive troubleshooting label, not a confirmed error string from the supplied source. Both inputs are required by the interface, so omitting either can prevent execution before the tool request is made.
- Solution: Supply both required inputs. Use a valid project identifier and argument text that follows your installed get_render schema; do not assume an empty string is accepted simply because the input type is STRING.
Argument preparation or tool invocation fails
- Explanation: The node prepares its arguments and invokes the tool without showing local error recovery. A failure in either step can therefore interrupt execution. Exact messages for malformed arguments, unrecognized project identifiers, or unsupported request fields are not included in the supplied context.
- Solution: Check the complete error in ComfyUI’s execution log, verify the project identifier, and compare your argument text with the installed tool schema. If that schema requires JSON, check quotation marks, commas, and brackets with a JSON validator.
Render setup failed: …
- Explanation: This message is present in the accompanying renderer and indicates that initialization in the browser-based rendering engine failed. It is not generated directly by the get_render wrapper and is relevant only if the underlying workflow surfaces a renderer failure.
- Solution: Read the message following the prefix for the specific cause. Check the project’s rendering document and referenced resources, correct the reported issue, and retry the rendering operation before requesting its result again.
Render failed at frame …
- Explanation: The accompanying renderer uses this message when rendering fails at a particular frame. The reported frame number identifies where processing stopped, and the remaining message contains the underlying browser-side error.
- Solution: Inspect the layers, assets, transitions, and custom hooks used at that frame. Fix the specific problem reported in the error, then render again. This node has no exposed frame-selection or repair controls.
not deterministic — frames … differ when rendered in reverse order
- Explanation: The supplied page renderer raises this error when sampled frames produce different image data depending on rendering order. This means the page does not reproduce the same frame consistently, which prevents a reliable render.
- Solution: Make the page’s animation depend on the requested frame and time rather than on previous frames, uncontrolled randomness, or elapsed wall-clock time. Ask whoever maintains custom page scripts or hooks to check this behavior, then rerun the render. This is a page-renderer error, not a validation rule implemented by get_render itself.
