Why did my new product prompt not reach the final video when I reran a Spaces node?

1. Distinguish an edited instruction from a newly generated asset

Illustrative exercise: the V1/V2 bottle references and lineage review are fictional; no account, node, generation, credit or export test was performed. The required V2 label must come from an approved updated product photograph, not an instruction to invent or repaint its printed wording.

Imagine a product workflow containing a Text node with packaging instructions, an image-generation node producing the approved bottle still, a Video Generator creating motion, and a final processing node. The merchant changes the required label from V1 to V2, then runs only the video node. The text instruction may have changed while the video node's available image input remains the previously generated V1 still.

The important distinction is between an instruction revision and a generation revision. Record what changed, which node produced the image, and which image result was available to the video step. A changed prompt is not evidence that the corresponding still image was regenerated.

Avoid diagnosing from the finished clip alone. A visible V1 label may indicate an older input, a newly generated image that failed to reflect the instruction, or another production issue. These explanations require different corrective actions.

2. Select the run scope that matches the intended change

Magnific Spaces documents three relevant choices. Run Node executes the selected node using the data already available at its inputs. Run Workflow executes the connected workflow. Run Downstream executes the selected node and its downstream dependencies while skipping upstream nodes.

Branch A — The product reference changed: replace the approved V1 bottle reference with the actual approved V2 photograph. If choosing Run Workflow, expect the entire connected chain from start to finish, including other connected branches; it is not an automatic affected-branch-only operation. For a smaller run, start at the first node that must produce updated material and confirm its inputs. Check the new still depicts V2 before accepting downstream motion.

Branch B — The product still is deliberately frozen: The V1 image remains approved, but the merchant wants a different camera movement. Start at the motion-generation stage and use Run Downstream to avoid unnecessarily regenerating upstream product imagery. The approved still remains the intended source.

Run Node is appropriate for an isolated step when its current inputs are acceptable. However, executing that step does not establish that later nodes were refreshed. Choose execution scope from the change requirement, not from which button seems fastest.

3. Reconstruct the lineage before assigning blame

Keep a short merchant editing note of the intended product reference, producing node, actual result supplied downstream and available generation identifier. This is a proposed review record, not a claim that Spaces exposes a separate native input-revision panel. Its documented generation history lets you inspect the settings used for a generation; compare the relevant actual records rather than trusting the latest thumbnail.

For the bottle example, ask whether the image supplied to the video step actually depicts V2. If it still depicts V1, investigate the upstream execution scope. If it depicts V2 but the final clip does not, investigate the video-generation result and the selected inputs.

Do not assume that selecting an older history entry automatically pins every connection to that revision. Record the source actually used. Similarly, do not infer hidden retries, credit charges, or refund behavior from the run-mode description.

4. Establish a merchant approval gate

Before requesting a new run, define the visible acceptance criteria: exact bottle-label revision, required product silhouette, approved still-image identity, intended motion, and the final clip's source record. Separate approval of the still from approval of the moving result.

For Branch A, approval requires evidence that the changed reference reached the newly generated still and that the intended still was supplied to the video stage. For Branch B, approval requires evidence that the fixed still remained unchanged while the requested motion revision was evaluated.

A proposed review can use side-by-side screenshots and recorded generation identifiers. These are acceptance artifacts to collect, not receipts from completed testing. Confirm expected credit implications in the actual interface before running; no cost or successful outcome is assumed.

Product Reference Lineage and Run-Scope Decision

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)