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 · Inspect composition

ComfyUI Node: OpenKatana · Inspect composition

Class Name

OpenKatana_inspect_composition

Category
OpenKatana/Tools
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 · Inspect composition Description

Validates compositions and inspects rendered frames, layout metrics, and font coverage.

OpenKatana · Inspect composition:

OpenKatana_inspect_composition checks a composition in a browser-based rendering environment so you can review its structure and measured layout before continuing with your creative workflow. It validates the composition, expands reusable components, displays the requested animation frame, and collects layout information together with font-coverage details. It can also save a transparent-background preview for visual review. This combines structural checks with an inspection of the rendered design, helping you investigate composition problems and review how a layout behaves at different canvas sizes. Component expansion is checked for repeatability, and browser runtime problems are reported rather than silently ignored. Inspection evaluates a particular frame and canvas size; it should not be treated as proof that every frame or responsive layout has been checked.

OpenKatana · Inspect composition Input Parameters:

project_id

A required STRING identifying the project used when preparing the tool request. The node passes this value to its argument-preparation layer together with the tool name and the supplied arguments. Use the identifier associated with the project you intend to inspect, keeping it consistent with the rest of your OpenKatana workflow. The provided code does not show how this identifier maps to a project directory, so it should not automatically be treated as a filesystem path. No default value, length limits, allowed-character rules, or list of accepted identifiers is provided.

arguments

A required STRING containing the tool arguments that the node prepares and sends to the inspection tool. Supply the serialized argument payload expected by your OpenKatana installation, rather than ordinary descriptive text. The underlying inspection function accepts a project root and a composition document, with optional settings for the frame, canvas dimensions, and a preview destination; these are tool-level settings, not additional node sockets. At that function level, the frame defaults to 0 and must be an integer from 0 through the composition’s frame count minus one; width and height default to the composition’s canvas dimensions and, when supplied, must each be integers from 16 to 7680; preview defaults to no saved screenshot. When a preview destination is supplied, its parent directories are created if needed, and the screenshot is taken with the background omitted and browser animations disabled. The provided node code does not expose the complete argument serialization or project-resolution contract, so follow the tool’s argument schema when packaging these settings. No default string value, string-length limits, or fixed options are shown for this socket.

after

An optional STRING accepted by the node, with a Python default of None when omitted. In the supplied execution method, this parameter is not read or passed to argument preparation or tool invocation, so no direct effect on inspection settings or report contents is demonstrated. Do not use it to specify a frame, preview path, or composition document. Any workflow-ordering behavior provided elsewhere by OpenKatana is not shown in the supplied code. No string-length limits, accepted-value list, or other constraints are provided.

OpenKatana · Inspect composition Output Parameters:

result_json

A STRING carrying the response produced by the tool invocation through the node’s response formatter. The successful underlying inspection result contains valid, browser, canvas, frame, layout, inputs, expanded, revision, and preview_images. Here, valid is set to true when inspection completes successfully; browser identifies the browser version; canvas describes the inspected canvas, including any dimension overrides; and frame identifies the inspected frame. The layout report contains the browser’s measurements and an added font_coverage entry, although the supplied code does not define their complete internal structure. The inputs entry lists composition input resources, while expanded contains the composition after component expansion. The revision value is a fingerprint of the original composition document, not a fingerprint of the rendered screenshot. The preview_images entry contains an absolute preview-file path when a preview was requested, or an empty list otherwise; it does not deliver a ComfyUI IMAGE output. The response formatter’s exact outer structure is not shown, so check the returned response before assuming these fields appear at its top level.

OpenKatana · Inspect composition Usage Tips:

  • Start with frame 0 and the composition’s original canvas dimensions to establish a baseline. Then inspect specific frames or alternate sizes separately so you can identify which change caused a layout difference.
  • For responsive designs, supply width and height overrides through the tool argument payload according to its schema. Each must be an integer between 16 and 7680. Test sizes around your responsive breakpoints rather than assuming one successful inspection covers all screen sizes.
  • Request a preview when you need to compare the measured layout with the visible design. Choose a writable screenshot destination; the inspection function creates missing parent directories and returns the saved file’s absolute path.
  • Leave the preview destination unset when you only need validation and measurement information. This skips the screenshot-writing step and leaves preview_images empty.
  • Use both the rendered preview and the layout report when investigating text issues. The report includes font-coverage information, but its detailed schema is not supplied, so interpret its fields alongside the actual appearance rather than assuming a particular warning format.
  • Keep component expansion repeatable. The inspection process expands the same composition twice and rejects it if the two expanded results have different fingerprints.
  • Remember that a successful report concerns the selected frame only. For animation review, run additional inspections at important moments such as the beginning, transitions, and final frame.
  • Keep the node structure within the documented validation limits: no more than 1000 visited nodes and no traversal depth greater than 24. Give every node a unique ID and use only the supported node types.

OpenKatana · Inspect composition Common Errors and Solutions:

Composition exceeds depth/node limit

  • Explanation: Composition validation found a traversal depth greater than 24 or counted more than 1000 nodes. Large designs or heavily nested component structures can exceed these limits.
  • Solution: Reduce unnecessary nesting and simplify repeated structures. If the design is very large, split it into smaller compositions that can be inspected separately.

Duplicate node ID: ...

  • Explanation: Two or more nodes have the same ID. The composition requires unique identifiers so individual elements can be distinguished.
  • Solution: Assign a different ID to every node. Check duplicated groups and reusable components for IDs copied without being renamed.

Unknown node type

  • Explanation: A node’s type is missing or is not one of the supported values: box, text, image, or component.
  • Solution: Check the type spelling and use one of the supported values. Put reusable component references in a node whose type is component rather than using the component’s name as the node type.

Fields not applicable to ...

  • Explanation: A node contains properties that are not permitted for its type. For example, children is a box-specific property, text and runs are text-specific properties, src is image-specific, and component and params are component-specific.
  • Solution: Remove or relocate the fields listed in the error. When changing a node’s type, also remove properties left over from its previous type.

dir: auto, ltr or rtl

  • Explanation: A node’s text-direction setting uses an unsupported value. The accepted values are auto, ltr, and rtl.
  • Solution: Use auto for automatic direction detection, ltr for left-to-right content, or rtl for right-to-left content.

Component expansion is not deterministic

  • Explanation: Expanding the same composition twice produced results with different fingerprints. Inspection requires reusable components to produce repeatable expanded structures.
  • Solution: Review the component or plugin responsible for expansion. Remove dependence on changing time, uncontrolled randomness, or other changing state, and ensure the same composition and parameters generate the same result.

Composition operation timed out

  • Explanation: A browser-side composition operation did not finish within the 30-second timeout shown in the source.
  • Solution: Try a simpler composition to isolate the problem, reduce expensive component work, and check required resources. If the issue occurs only with a particular component or plugin, inspect that implementation before retrying.

Composition runtime: ...

  • Explanation: The runtime detected a browser error, blocked request, HTTP error response, or recorded runtime violation. The message combines the detected problems and may include details such as HTTP 404: ....
  • Solution: Read the details after the prefix. For HTTP errors, check resource paths and file availability; for blocked requests, use resources permitted by the project’s loading rules; for script errors, review the relevant component or plugin.

Invalid frame value

  • Explanation: The inspection function validates that the frame is an integer between 0 and the canvas frame count minus one. This heading describes the condition; the exact error wording from the numeric validator is not provided.
  • Solution: Choose a whole-number frame in the supported range. For example, a composition with 24 frames accepts frame indices 0 through 23, not 24.

Invalid width or height value

  • Explanation: Canvas dimensions are validated as integers from 16 through 7680. Values outside that range, fractional numbers, or unsuitable data types fail validation; the exact numeric-validator message is not shown.
  • Solution: Supply whole-number dimensions within the allowed range, or omit the overrides to use the composition’s own dimensions. If the original dimensions are invalid, correct the composition document.

unexpected inputs: ...

  • Explanation: The node explicitly rejects extra keyword inputs that are not declared in its typed input definitions. Tool settings such as frame and preview are not listed as separate sockets in this node interface.
  • Solution: Use only project_id, arguments, and the optional after input. Package inspection settings inside arguments according to the tool’s expected schema rather than adding custom node inputs.

OpenKatana · Inspect composition 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 · Inspect composition