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 > MiniMaxH3-Studio > H3 Context Audit Override

ComfyUI Node: H3 Context Audit Override

Class Name

comfyui_h3_context.H3Context.AuditOverride

Category
h3_context/audit
Author
rookiestar28 (Account age: 1077days)
Extension
MiniMaxH3-Studio
Latest Updated
2026-11-05
Github Stars
0.16K

How to Install MiniMaxH3-Studio

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

H3 Context Audit Override Description

Applies traceable manual edits to H3 Context prompts, preserving plans and revalidating changes.

H3 Context Audit Override:

This node lets you make an explicit, traceable manual edit to an H3 Context prompt while keeping its original typed plan intact. It is designed for the review stage, when you want to refine wording without silently replacing the planning information or bypassing validation. Each edit is associated with a report fingerprint, a revision number, and a reason, helping you identify which reviewed version the change belongs to and why it was made. The node checks that the edit targets the correct report and revalidates the edited prompt against the source plan without executing a provider request. This makes it useful for controlled artistic refinements where you need both creative flexibility and a clear audit trail. It does not generate images or video, and a manual override should not be treated as permission to ignore the plan’s constraints.

H3 Context Audit Override Input Parameters:

report

Required input of type H3_CONTEXT_REPORT. This is the source report you reviewed in H3 Context Preview and want to edit. It supplies the existing prompt, source-plan context, and report information used to apply and validate the manual revision. You must connect an actual H3 Context report rather than a text prompt, preview string, or other object; the node explicitly checks its type. Use the same report whose fingerprint you copied from the audit preview, because a fingerprint from a different report will not identify the correct editing target. No default value, numerical range, or selectable options are specified.

base_report_fingerprint

Required STRING input with a default of an empty string. Enter the exact report fingerprint shown by the audit preview for the connected report. A fingerprint acts like an identifying stamp for a particular report state, allowing the node to detect an edit prepared against an outdated or different report. This protects you from unintentionally applying changes to a version you did not review. Copy the value exactly rather than substituting a report ID, workflow fingerprint, or descriptive label. No minimum or maximum string length is exposed in the node interface; the empty default is a placeholder, not a fingerprint you should use for a normal edit.

revision

Required INT input identifying the operator revision for this manual edit. The default is 1, the minimum is 1, the maximum is 1000000, and the step is 1. The applied override’s revision becomes the revision of the updated report, so this value helps distinguish and track your manual changes. Use a clear numbering convention when making successive edits, and use the fingerprint of the report you are currently revising. The node requires a genuine integer; a boolean value such as True or False is explicitly rejected even when supplied through a programmatic workflow.

reason

Required STRING input with the default Operator-approved audit edit. This records why you are making the manual change, giving the override useful review context instead of leaving it as an unexplained prompt replacement. For example, you could write “Clarify camera movement while preserving the original subject and timing.” The interface specifically advises against including credentials or URLs, so keep this field focused on the creative or editorial reason for your edit. No minimum or maximum length is shown in the interface; the supplied context references a reason-length limit internally but does not provide its numerical value.

prompt_text

Required multiline STRING input with a default of an empty string. This is the exact caller-authored prompt text you want applied to the report, not an instruction asking the node to rewrite the existing prompt. Supply the complete intended prompt rather than only a description of the change. The node revalidates this text unchanged, and dynamic prompt expansion is disabled with dynamicPrompts=False, making the submitted wording explicit and predictable. Preserve the requirements established by the source plan when editing, especially any hard constraints or exact text requirements. No minimum or maximum length is exposed in the interface; the supplied context references an internal text-length limit without specifying its value.

H3 Context Audit Override Output Parameters:

edited_prompt

Output of type H3_PROMPT_STRING containing the text of the updated report’s prompt document. This is the prompt text produced by the applied manual revision, not an AI-generated rewrite or a summary of what changed. It provides the text-oriented result for compatible downstream connections. Although its underlying returned value is a string, its declared ComfyUI socket type is H3_PROMPT_STRING, so check socket compatibility before connecting it to another node. The prompt text alone does not contain the report’s validation details or audit context.

updated_report

Output of type H3_CONTEXT_REPORT containing the revised report. It includes the updated prompt document, the override’s revision number, a report ID derived from the override ID, updated validation information, and a provider receipt while preserving the typed plan. Existing diagnostics are retained, and an informational diagnostic with code audit_override_applied is appended to record that the manual prompt override was applied and revalidated. This is the main output to inspect when reviewing the revision in context, rather than looking only at the edited text. Revalidation is part of the operation, but you should inspect the resulting validation information rather than assume that a manually edited prompt satisfies every requirement.

override

Output of type H3_AUDIT_OVERRIDE representing the explicit manual edit built from the supplied report fingerprint, revision, reason, and prompt text. It serves as the structured audit record of your editing decision, separate from the report that results from applying it. This distinction is useful when you need to track what you requested and why, rather than only examining the final prompt. It is a typed object for compatible workflow connections, not a plain text explanation or a generated image.

prompt_document

Output of type H3_PROMPT_DOCUMENT containing the updated report’s structured prompt document. It carries the edited prompt in the document form expected by compatible H3 Context nodes, rather than exposing only its text. Use this output when the next step requires a prompt document, such as an explicit H3 Context Validator step that also receives the relevant plan. The text inside this document is the same text returned through edited_prompt, but the two outputs have different socket types and purposes.

H3 Context Audit Override Usage Tips:

  • Review the source report in H3 Context Preview before editing, then copy its exact report fingerprint into base_report_fingerprint. Keep the preview and connected report synchronized to avoid stale-edit failures.
  • Enter the complete desired prompt in prompt_text. For example, replace an ambiguous camera description with precise wording while retaining the rest of the prompt’s required content; do not enter only “make the camera movement clearer.”
  • Preserve the source plan’s constraints. If the plan requires particular wording, a subject, or another hard requirement, a manual edit should retain it rather than attempting to bypass validation.
  • Use revision consistently to distinguish edits, starting with the default 1 when appropriate. When editing an already revised report, obtain the fingerprint for that revised report rather than reusing the original fingerprint.
  • Write a specific, non-sensitive reason such as “Remove ambiguous lighting wording while preserving the planned scene.” Avoid credentials and URLs, as directed by the field’s tooltip.
  • Inspect updated_report after the edit to review validation information and diagnostics. If your workflow includes a separate validator, connect prompt_document to it along with the relevant plan rather than substituting the text-only output.
  • Treat this as an editing and validation step, not a generation step. It does not execute a provider request; connect its results to the appropriate later workflow stages when you are ready to continue.

H3 Context Audit Override Common Errors and Solutions:

report must be a ContextReport

  • Explanation: The node received an object that is not a valid H3 Context report. This error uses the diagnostic code invalid_report and can occur when a prompt string, document, or unrelated output is connected in place of a report.
  • Solution: Connect a compatible H3_CONTEXT_REPORT output, such as the report produced by H3 Context Compiler. Make sure it is the report you reviewed in the audit preview.

base_report_fingerprint must be a string

  • Explanation: The fingerprint value has the wrong data type. This error uses the diagnostic code invalid_override and is particularly relevant when inputs are supplied through an API or constructed programmatically.
  • Solution: Supply the exact fingerprint as text. Do not pass a number, object, or an entire preview result in place of the fingerprint string.

revision must be an integer

  • Explanation: The revision was supplied as something other than an integer, or it was supplied as a boolean. The diagnostic code is invalid_override.
  • Solution: Use a whole number in the interface range of 1 to 1000000. In API requests, supply an integer rather than quoted text, a decimal, or a boolean.

reason and prompt_text must be strings

  • Explanation: At least one of these fields contains a non-text value. The node reports this with the diagnostic code invalid_override before attempting to build the override.
  • Solution: Provide ordinary text for both fields. When building requests programmatically, extract the intended text instead of passing a list, dictionary, or document object.

audit override failed closed

  • Explanation: This is the node’s protective failure message when building or applying an override fails. For an AuditOverrideError, the node preserves the underlying error code while displaying this message. A known cause described by the interface is a stale edit whose fingerprint does not match the connected report; other override validation failures can use the same general message.
  • Solution: Check the accompanying diagnostic code first. Refresh the audit preview, copy the fingerprint for the currently connected report, confirm that the revision is valid, and review the reason and complete prompt text. Do not assume an override was successfully returned after this error.

override_failed: audit override failed closed

  • Explanation: The node uses override_failed for certain report-processing, type, or value failures that do not arrive as a more specific override error. The core implementation can also report manual override validation failed closed under this code. These messages indicate that the edit could not be completed safely, rather than that a provider generation failed.
  • Solution: Recheck the source report, fingerprint, revision, and edited text together. If necessary, regenerate the report through the upstream H3 Context workflow, preview it again, and retry a small edit that preserves the plan’s requirements. Use the accompanying diagnostics to investigate any remaining validation issue.

H3 Context Audit Override Related Nodes

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

H3 Context Audit Override