A China-based production partner reports that your product-video batch has finished. The tracker contains links, but several stop working before your overseas marketing team reviews the assets. Pressing “retry all” may produce another batch without correcting the failed file-receipt step.
Before treating a missing link as a request for new creative, establish where the original output went. ONCE proposes separate records for generation, receipt, registration and approval. They describe different kinds of completion.
Easier integration does not remove the handover step
On November 2, 2026, Runway announced Runway Dev plugins for coding agents, including Claude Code, Codex and Cursor. This establishes an integration offering; it does not establish that every customer has a reliable production pipeline or commercially approved output.
Runway Dev’s API Output Formats, checked November 3, says generated output links expire within 24–48 hours of API access and should be downloaded to the developer’s own storage rather than exposed directly in a product. That is a rule for these API output links, not a universal retention rule for all AI tools or the Runway web library.
The Workflow documentation also describes expiring output URLs and retrieving the original invocation again for fresh links. Do not assume every endpoint offers the same recovery behavior, or interpret an expired URL alone as proof that the underlying asset has been permanently deleted.
Use four receipt milestones
| Milestone | What the record should establish |
|---|---|
| Generated | The original task or invocation, input version and expected outputs match the returned result |
| Received | The agreed file is fully saved in the designated destination and can be read |
| Registered | The saved asset maps to the product, shot, version and original task |
| Approved | A named reviewer accepts or returns it for the specified use |
These are ONCE’s proposed project milestones, not new Runway statuses. Generation success, transfer completion and creative acceptance must remain distinct.
For receipt, confirm the file exists and opens, check duration and media properties against the expected output, and examine essential pictures and audio. File size and checksums can support transfer verification. A matching checksum does not establish accurate product representation, creative quality or complete usage rights.
Agree who controls storage, who can retrieve the files, how long they remain available and how handover works if the engagement ends. Storage need not be public. A temporary URL may be a retrieval mechanism; it should not be the only identifier for the asset.
Retry the failed step, not automatically the generation
Look for an existing saved copy
If the file was received but the tracker still points to an old temporary URL, repair the index or access configuration. A changed link is not a new product-video version. Test access for the intended recipient rather than relying on the production partner’s own account.
Check retrieval against the original record
Without a saved copy, retain the task or invocation identifier and investigate the current service’s supported retrieval path. For the Runway Workflow behavior documented above, retrieve the original invocation for fresh URLs, then download and verify the files. Actual recovery depends on access and service conditions; this is not a promise of indefinite availability.
Consider regeneration only when recovery or content requires it
Record why retrieval is unavailable before commissioning replacement work. If the brief has changed, distinguish a new generation from an edit or removal from scope. Regeneration can produce different content; it does not restore the original approved clip. A replacement needs its own review.
Separate repeated downloads from repeated generation in the work order. Reconcile platform charges, recovery labor and creative rework against the actual contract. An internal receipt failure should not automatically become a new production charge to the client.
A hypothetical batch shows the difference
Suppose 20 travel-product clips have generated outputs. Sixteen have been fully saved; four have no received copy. These numbers illustrate the method and are not an ONCE project, test or platform success rate.
Verify the sixteen receipt records and attempt retrieval of the other four. If three are recovered and one is confirmed unavailable, only the final item needs a regeneration decision. That assumes the brief is unchanged and the saved content meets subsequent review requirements. Changed content belongs on a separate revision list.
Keep the disposition of all twenty: saved location, recovery record, unresolved or irrecoverable result, and any replacement linked to its original item. Nineteen retrievable clips are not automatically nineteen approved clips. A green batch total should not conceal that distinction.
Ask the supplier to demonstrate a receipt failure
Before scaling, agree a small, authorized test that deliberately interrupts the saving step in a test environment. Check whether the workflow retains the original generation record, identifies exactly which files were not received and recovers only the missing receipt steps afterward. Set the scope and any fees in advance; do not experiment on a live launch batch. No such test was performed for this article.
A useful acceptance demonstration resumes from the failure point. A smooth end-to-end generation demo alone cannot establish that capability. Name the alert recipient, recovery owner, response commitment and fallback when the original result cannot be recovered. A 24–48-hour URL lifetime does not itself promise the client an equally long recovery window.
Long-term archive retrieval and editable-project restoration are additional services. For related planning, browse ONCE’s production guidance. This article addresses the initial transfer into an asset library, not every backup or rights-management requirement.
Measure usable handover alongside generation
For ongoing content production, retain generation costs, receipt exceptions, review decisions and actual adoption separately. That makes it possible to investigate whether spend created new material or repeated work. Any claimed margin or productivity improvement would need project evidence.
When briefing ONCE for batch AI video, add one practical request: “Show where the outputs are saved, and how a failed receipt is recovered without rerunning the whole batch.” That defines a deliverable your marketing team can use.
Sources were checked November 3, 2026. The plugin announcement is dated November 2; the two API documentation pages do not display publication dates. The four milestones, test design and numerical scenario are ONCE analysis. The original AI cover illustrates the topic rather than depicting a client handover.
