H3 Context Request:
The H3 Context Request node establishes a validated starting point for an H3 context workflow by organizing your creative instructions into a consistent, typed request. It creates an immutable request envelope, meaning the recorded request is not intended to be edited in place after creation, helping later stages work from a stable description of what you want to achieve. This node focuses on capturing and checking the request rather than generating media, enhancing a prompt, or attaching reference materials. Reference binding and prompt compilation are handled by later nodes. Its main benefit is separating the definition of your creative task from the processing that follows, while reporting request-validation problems instead of silently substituting a fallback request.
H3 Context Request Input Parameters:
task_mode
Required selection that explicitly identifies the H3 task mode for the request. Its type is COMBO, and its available choices are supplied by TASK_MODE_CHOICES. The default is TaskMode.T2VA.value; the supplied source does not show the literal value of that default or enumerate the other choices, so a complete option list cannot be reliably reproduced here. Select the appropriate entry from the node’s displayed menu rather than guessing a mode name. This setting is passed into request construction and validation, making it part of the task definition that later workflow stages receive. Numeric minimum and maximum values do not apply.
user_intent
Required text field containing your description of what you want to accomplish. Its type is STRING, its default is an empty string, and it supports multiple lines so you can clearly separate scene details, actions, and creative instructions. Dynamic prompt processing is disabled through dynamicPrompts: False, and the field’s tooltip explicitly states that exact hard text is preserved. This makes it suitable for recording instructions whose wording matters without having this field perform dynamic prompt expansion. No minimum or maximum text length is declared in the supplied interface; an empty default should not be interpreted as confirmation that every empty request will pass the underlying validation. The text becomes part of the request rather than an automatically enhanced or compiled prompt.
duration_seconds
Optional expected duration, expressed in seconds, with type FLOAT. The declared minimum is 0.0, the maximum is MAX_ACCEPTED_MILLISECONDS / MILLISECONDS_PER_SECOND, and the adjustment step is 0.01 seconds. The numeric value of the maximum is not included in the supplied source, so use the limit shown in your installed node rather than assuming a 150-second maximum. No widget default is explicitly declared; the request-building method uses None when this argument is omitted. When supplied, the duration is used to derive an H3 frame count, which is snapped to the permitted 17k+5 pattern rather than treated as an unrestricted frame total. Consequently, the resolved frame-based duration may not exactly match your entered number. Although the control permits zero at its lower boundary as an unset-style display value, the source explicitly states that zero is rejected by validation when submitted as a duration.
hard_constraints
Optional connection with type H3_HARD_CONSTRAINTS for supplying an immutable set of hard constraints from a compatible typed node. It lets you include explicit requirements alongside your creative intent in the request, rather than representing everything only as free-form prose. The supplied context identifies comfyui_h3_context.H3Context.HardConstraintProducer as a producer of this socket type. No widget default, numeric range, or selectable options are declared; when omitted from the method call, the value is None. Connect a correctly typed constraint set when your workflow needs one, or leave this connection unused when it is not needed. This node includes and validates the supplied data as part of request construction; it does not itself generate media or demonstrate that a later generation will satisfy every requirement.
H3 Context Request Output Parameters:
request
The single output, with type H3_CONTEXT_REQUEST, contains the validated RawContextRequest envelope built from your request settings. This is a structured workflow object, not a finished prompt, image, video, or human-readable report. It carries the task definition forward so compatible downstream nodes can perform subsequent context-processing steps, including reference binding and prompt compilation. Its immutable design provides a stable request for those later stages. If canonical request construction fails, the node reports the validation problem rather than returning a substitute request, so a successfully produced connection represents a request that passed this node’s construction checks.
H3 Context Request Usage Tips:
- Choose
task_modefrom the node’s actual dropdown. The supplied source does not list all supported choices, so copying an assumed mode identifier from elsewhere can introduce validation problems. - Write
user_intentas a clear creative brief, for example: “A slow camera push toward a ceramic vase on a sunlit table; keep the background still.” Use separate lines for distinct instructions when that improves readability. - Keep wording that must remain exact directly in
user_intent. Dynamic prompt expansion is disabled here, but remember that this node preserves the request rather than guaranteeing how every later processing stage will handle the text. - If duration is not needed, omit
duration_secondswhere your workflow allows it. Do not submit0as a substitute for an omitted duration, because the source explicitly identifies zero as invalid during validation. - When duration matters, select a positive value within the displayed range and allow for frame-count snapping. The
0.01-second control step does not mean the final frame-based duration can represent every hundredth of a second exactly. - Connect
hard_constraintsfrom a compatibleH3_HARD_CONSTRAINTSproducer when you need a structured constraint set. An ordinary text connection is not interchangeable with this typed connection. - Send
requestto a compatible request-consuming node. Add reference binding and prompt compilation in later stages rather than expecting this node to attach media or produce an enhanced prompt.
H3 Context Request Common Errors and Solutions:
Request validation failed — diagnostic wording varies
- Explanation: The node catches
CanonicalContextPipelineErrorduring request construction and exposes its diagnostics throughRequestNodeError. The supplied code does not contain the underlying diagnostic strings, so this heading describes the failure category rather than quoting a literal error message. Validation returns the reported error instead of creating a fallback request. - Solution: Read the diagnostic shown by ComfyUI and correct the named setting or connection. Start with a dropdown-selected task mode, clear intent text, and no optional connections, then reintroduce optional settings one at a time.
Invalid task mode — descriptive error category
- Explanation: The request requires an explicit task mode. A missing or unsupported value, such as one introduced by an edited workflow or external call, may be rejected by the canonical request builder. The exact message and complete accepted-value list are not present in the supplied source.
- Solution: Re-select the mode from the installed node’s dropdown. If you call the node programmatically, use a value from the installed
TASK_MODE_CHOICESrather than an assumed label.
Zero duration rejected — descriptive error category
- Explanation: The source explicitly says that
0.0is retained as the control’s lower boundary for an unset-style display, but zero is rejected by validation. A displayed zero and an omitted optional argument are therefore not equivalent when the value is submitted. - Solution: Enter a positive supported duration, or omit the optional duration through the mechanism available in your workflow. For a direct method call, omission uses
None.
Duration outside the supported range — descriptive error category
- Explanation: Duration must fit the supported limits after conversion to a permitted H3 frame count. The source notes that the earlier 150-second bound admitted durations whose aligned frame counts exceeded the supported range, and that the maximum was reduced accordingly. The exact validation wording is not supplied.
- Solution: Use a positive value at or below the maximum displayed by the current node. If an older workflow contains a duration near 150 seconds, reduce it to the installed node’s accepted range.
Incompatible hard_constraints connection — descriptive connection or validation problem
- Explanation: This input expects
H3_HARD_CONSTRAINTScontaining a typed constraint set, not an ordinary string or an unrelated context object. An incompatible connection can be blocked by ComfyUI or fail request validation; the supplied class does not specify a literal error message for this case. - Solution: Connect a compatible hard-constraint producer, such as
comfyui_h3_context.H3Context.HardConstraintProducer, or leave the input unconnected. Put ordinary creative instructions inuser_intent.
Incompatible request output connection — descriptive connection problem
- Explanation: The output is an
H3_CONTEXT_REQUESTobject, not aSTRINGprompt or media output. Connecting it directly to a socket expecting another type does not perform prompt compilation or media generation. - Solution: Route it to a downstream socket that explicitly accepts
H3_CONTEXT_REQUESTand complete the later context-processing stages required by your workflow.
