H3 Full-Reference Plan:
The H3 Full-Reference Plan node bridges an accepted Full-Reference timeline and the H3 context compilation pipeline. Rather than creating a new plan or changing an existing timeline, it adopts the plan already prepared by the timeline stage and checks that it belongs to the required Full-Reference profile and REF2VA task mode. It also prepares an initial report that preserves diagnostic information from the timeline stages, helping you carry planning feedback forward. This makes it useful when you want to move an established Full-Reference timeline into the subsequent compilation and validation stages without rebuilding its plan. Its responsibility is deliberately limited: it does not compile the final prompt document, perform downstream validation, generate media, or connect native media resources.
H3 Full-Reference Plan Input Parameters:
timeline
Required input of type H3_FULL_REFERENCE_TIMELINE. This connection must supply a FullReferenceTimelineResult, the structured result of the Full-Reference timeline stage, rather than plain text or an ordinary context plan. For execution to succeed, the result must be marked valid and contain both a plan and a timeline. The embedded plan must use the FULL_REFERENCE prompt profile and the REF2VA task mode; otherwise, the node rejects it instead of converting it automatically. When accepted, the existing plan is passed onward unchanged, while diagnostic information from both the overall result and its embedded timeline is included in the initial report. This is a connection-based parameter with no declared default, numerical minimum or maximum, or selectable options.
H3 Full-Reference Plan Output Parameters:
plan
Output of type H3_CONTEXT_PLAN. This is the same plan contained in the accepted Full-Reference timeline result, not a newly generated or revised plan. It provides the planning object for subsequent H3 pipeline stages, such as context compilation. Receiving this output means that the timeline result passed this node’s validity, completeness, and profile checks; it does not mean that downstream compilation or validation has already succeeded. Keeping the original plan intact preserves the planning decisions made by the upstream timeline stage.
report
Output of type H3_CONTEXT_REPORT. This is an initial pipeline report created for the accepted plan using a draft prompt document and a validation state indicating that validation has not yet run. It includes diagnostic information collected from both the Full-Reference timeline result and its embedded timeline, so you can retain upstream feedback as the plan moves through the workflow. Treat it as a planning-stage report rather than a final approval or proof that a compiled prompt is ready for generation. If the node cannot construct this report successfully, execution raises an error instead of returning the outputs.
H3 Full-Reference Plan Usage Tips:
- Connect the structured result from the Full-Reference timeline stage, associated with H3 Full Reference Timeline Producer, to
timeline. A matching-looking text description or a regularH3_CONTEXT_PLANconnection is not a substitute for the required timeline result. - Set up the upstream planning workflow to produce the
FULL_REFERENCEprofile with theREF2VAtask mode. This node checks these settings but does not offer controls to change or repair them. - Resolve upstream timeline errors before running this node. The timeline result must be marked valid and include both its plan and timeline; having only one of these is insufficient.
- Continue with explicit downstream compilation and validation stages. The returned
reportstarts with validation not yet run, so successful execution here should not be treated as final validation. - Review the diagnostics carried in
reportwhen troubleshooting later stages. The node preserves diagnostics from both levels of the timeline result rather than discarding that context. - Make changes to timeline content or planning decisions upstream. This node has no tuning widgets or performance settings and passes the accepted plan through unchanged.
- Keep native media wiring as a separate downstream step. This node prepares the handoff to the context pipeline but does not attach media resources or generate an image, video, or audio result.
H3 Full-Reference Plan Common Errors and Solutions:
timeline must be a FullReferenceTimelineResult
- Explanation: The node received an object of the wrong kind. This error uses the diagnostic code
invalid_timelineand can occur if the supplied value is an ordinary plan, text, another custom object, or a missing value at execution time. - Solution: Connect a valid
H3_FULL_REFERENCE_TIMELINEresult from the Full-Reference timeline stage. Check that you selected the timeline-result output rather than a plan or report output.
Full-Reference timeline did not produce a renderable plan
- Explanation: The supplied object has the correct type, but it is marked invalid, does not contain a plan, or does not contain a timeline. The error uses the diagnostic code
invalid_timelineand includes the existing diagnostics from the timeline result, which may explain the upstream failure. - Solution: Inspect the upstream timeline stage and its diagnostic messages. Correct the reported planning or timeline problems, then rerun that stage so it produces a valid result containing both the plan and timeline.
Full-Reference timeline plan has an incompatible profile
- Explanation: The embedded plan does not satisfy the required combination of the
FULL_REFERENCEprompt profile and theREF2VAtask mode. This error also uses the diagnostic codeinvalid_timeline. A result can pass the initial timeline checks and still fail this profile check. - Solution: Check the upstream request and planning configuration, ensuring that both required settings are used, and regenerate the timeline result. This node cannot convert a plan from another profile or task mode.
Full-Reference timeline report construction failed
- Explanation: The timeline and profile checks passed, but creating the initial pipeline report failed with an underlying
ContextReportError,TypeError, orValueError. The diagnostic code istimeline_report_failed. The visible message alone does not identify which report data caused the problem. - Solution: Check the ComfyUI execution log for the underlying exception. Regenerate the upstream timeline result, especially if it was supplied by custom code or retained from an earlier workflow execution. If the error persists, include the underlying exception and the workflow details when reporting the issue to the extension maintainer.
