-
Notifications
You must be signed in to change notification settings - Fork 26
Review Resume and Recovery
Every scene is checkpointed before review. You can:
- Approve and continue to the next scene;
- Edit and retry the same scene with the active Plan/editor prompt;
- Reroll the same scene with a new seed;
- Approve and stop to keep a valid partial run.
The optional floating cancel action can stop and reroll the currently sampling scene. It does not discard an already accepted predecessor.
Keep the same run_name, reconnect the same generation dependencies, and set
start_clip to the desired scene. A bounded scene_range accepts one scene
such as 3 or one continuous range such as 3:8.
Resume verification compares saved and current scene dependencies. A mismatch report tells you which scene and field changed and whether regeneration is required. Future-scene or assembly-only changes do not invalidate an accepted predecessor.
Disabling verify_resume_history is an explicit expert override. It bypasses
Plan/history matching but still checks saved file hashes, tensor shapes, and
checkpoint consistency.
Run Manager can:
- browse saved runs;
- restore the saved Plan and prompt history;
- archive loader-backed reference assets under the run folder;
- reopen a run folder;
- recover the Source Timeline needed by assembly.
Load Manifest and Assemble can finish a completed or interrupted run without sampling again. Partial assembly joins all accepted scenes. Saved latents can also be re-decoded one scene at a time into a PNG sequence.
Run files live under:
ComfyUI/output/h3_chains/<run_name>/
A run may contain:
- accepted segment MP4 files;
- generated-audio WAV files;
- sampler AV latents and context metadata;
- Plan, prompt, seed, dependency, and workflow archives;
- earlier checkpoint revisions after a retry;
- archived reference assets and a recoverable Source Timeline;
- completed or partial assembled outputs.
Writes are atomic: an interrupted retry does not replace a previously valid checkpoint with a partial artifact.
Run Manager and the checkpoint browser can select an earlier scene revision. Restoring it also restores the matching prompt, seed, Plan values, and connected 0.5 policy state saved with that revision. Later revisions remain available.
Each scene records the assembly-only overlap entering it. Partial or recovered assembly can reconstruct the same blend schedule without rerunning diffusion. Legacy checkpoints without this metadata fall back to their original hard-trim behavior.
Next: Plan and scene authoring, Plan reference, or Troubleshooting.