What breaks if I send a workflow that uses subgraphs or subgraph blueprints to someone on an older ComfyUI frontend, and which minimum versions does the documentation state?

Problem: sharing a workflow with a collaborator on an older install silently loses structure. Conditions: recipient frontend older than the first subgraph release. Method: the user guide states subgraphs need frontend 1.24.3 or later, the parameters panel needs ComfyUI v0.3.66, and publishing a subgraph to the node library (blueprints) needs frontend 1.27.7. The frontend stamps extra.frontendVersion when converting a graph for the API, and the schema carries a version number whose bumps are handled in deserialisation. Pre-flight check: read definitions.subgraphs and any node whose type is a GUID; if the recipient frontend is below 1.24.3, expect those nodes to show as missing node types (a UUID is not a registered class); on intermediate versions, expect promoted widgets or blueprints to be missing. Safer alternatives: export API-format JSON (flattened, no subgraph dependency, but it loses layout and subgraph structure), or pin the same frontend package version on both sides. Failure modes: assuming the receiving frontend shows a helpful upgrade message (not verified); relying on a custom node pack that ships subgraph JSON when the pack is not installed. Limitations: the page says converting a subgraph back to nodes will come in the future while also documenting an Unpack action, so it is partly stale; what an old frontend actually displays was not tested. Version/date: fetched 2026-10-23. Curator qualifications: All cited documentation excerpts located on the live pages by curator GET; no video sources. Correction folded 2026-10-24 from C3-B709-04 (curator-reviewed discovery audit): Problem. C3-B617-05 states, as part of its Method, that the workflow schema carries a version number whose bumps are handled in deserialisation, that subgraphs live under definitions.subgraphs with nodes whose type is a GUID, and that API-format export is flattened but loses layout and subgraph structure. The evidence rows cited only the docs page and executionUtil.ts, which support the version numbers (1.24.3, 1.27.7) and the extra.frontendVersion stamp, not those other statements. Conditions. ComfyUI frontend at 2f4df30. Method (correction). The frontend workflowSchema.ts does show the shapes: the workflow object has version: z.literal(1) and an optional definitions with subgraphs, and subgraph definitions have a z.guid() id. It does not show that version bumps are 'handled in deserialisation', how an older frontend displays an unknown GUID node type, or what an API-format export drops. Those three remain unsourced inference and should be labelled so. Failure modes. Acting on an unlabelled claim about old-frontend behaviour. Limitations. Schema file only; no frontend was run. Version/date. Commit 2f4df30, fetched 2026-10-23. Limitations: What an older frontend does with a GUID node type is an inference from how unknown node types are generally reported; I did not test it. Version numbers are as printed in the docs and may lag the frontend repository. Corrected by C3-B709-04; where the correction disagrees, the correction governs. The unamended original was withheld and never admitted. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://docs.comfy.org/interface/features/subgraph",
      "note": "Intro note; Subgraph Blueprint; Intro note; graphToPrompt"
    },
    {
      "url": "https://raw.githubusercontent.com/Comfy-Org/ComfyUI_frontend/2f4df30c2520877544365e15719c296ae756e128/src/utils/executionUtil.ts",
      "note": "Intro note; Subgraph Blueprint; Intro note; graphToPrompt"
    }
  ]
}