Your production partner generates a product shot, but the connector moves to the wrong side. The file is complete and the platform has charged for it. The brand calls it a failed generation. That phrase conceals a distinction that matters to the next production decision.
ONCE recommends separating technical errors, outputs that miss approved requirements and changes to the brief. Record the reason before authorizing another batch.
Platform consumption and client acceptance are different events
Runway's Can I have credits refunded?, checked October 28, 2026, distinguishes generation errors eligible for automatic credit return from completed but unsatisfactory outputs that do not automatically receive credits back. This is the help page's service policy, not a universal rule for every model, API or provider.
In her October 27 analysis, Forrester's Tracy Woo argues that tokens and credits capture only part of AI ownership cost; labor, data and operations also matter. That is analysis, not an audit of video-production economics.
The procurement implication is our own: a platform's billable process and a supplier's deliverable need separate definitions. Neither should silently determine the other.
Case one: a technical error
Where a task explicitly errors without completing an output, retain its identifier, error and actual charge or return status. Before submitting again, establish whether the earlier task is still running. An absent visible result alone is insufficient evidence of a terminated task.
A credit return does not erase diagnosis, waiting or communication. Record consumption and human work separately rather than describing the entire retry as costless.
For persistent errors, check supported inputs, settings and service status before choosing a next step. Do not repeatedly submit prohibited content to bypass restrictions. Agree a project-specific review point rather than assuming unlimited retries.
Case two: a completed file misses the approved requirement
Wrong connectors, opening directions, identity or action continuity can make a finished file unusable. Point to the approved reference and specific deviation: “The reference places the connector on the right; this output moves it left.” That is more actionable than “bad result.”
The production lead should assess regeneration, controlled post work, CG or live action. Previous credit spend does not make another attempt more likely to succeed. Repeated critical deviations call for a method review.
In a fixed-deliverable project, normal platform charging does not by itself justify billing the client for every unusable attempt. Nor does it establish unlimited supplier effort. Define the promised outcome, included work, escalation and decision owner before production begins.
Case three: the brief changes
A product rotating against white and a person carrying it through rain are different requests. Compare the approved and revised tasks, identify reusable work and confirm additional scope, timing and fees before proceeding.
Do not classify every review note as a change. Correcting a previously specified product feature differs from adding a new scene. Refer disputed cases to the approval record and project owner rather than leaving the generation operator to decide alone.
| Reason | Check first | Next decision |
|---|---|---|
| Technical error | Task, error and billing records | Diagnose, wait or retry within limits |
| Approved requirement not met | Reference and concrete deviation | Correction method, route and responsibility |
| Changed requirement | Scope difference and retained work | Approve additional work before execution |
This is ONCE's management classification, not a platform refund rule or an automatic allocation of payment responsibility.
Set a batch limit and a review point
Before each batch, identify one problem to resolve, the fixed references, permitted consumption or spend, review time and who can authorize continuation. Use actual project constraints rather than an invented industry success rate.
At the limit, stop further consumption and present the available results and unresolved issue. Options include another authorized batch, revised inputs, a different production route or stopping that shot. A budget limit is not permission to accept incorrect product facts.
Distinguish a feasibility or concept exploration from a promised finished film. Exploration may deliver directions, samples and a feasibility judgment. A fixed output cannot be replaced by a folder of attempts. The stages can connect while retaining their own scopes.
Keep consumption, effort and acceptance visible
For each batch, retain net consumption, operating and review time, correction work and acceptance status. Mark pending refunds as pending. Do not add work already included in a service fee again as a separate cost.
Compare what remains necessary to complete the same shot, rather than the cheapest individual generation. For an overseas team working with a Chinese production partner, this record can make a difficult remote review more concrete: what went wrong, what stays fixed and what is authorized next.
Recurring content operations can learn which requirements repeatedly need another method and what each batch actually consumes. Do not present those records as a stable success rate or guaranteed margin before validation. Further guidance is available in the ONCE video marketing articles.
Sources and limits
Sources were checked on October 28, 2026. The Runway help page is undated; the Forrester article is dated October 27. The classification and batch controls are ONCE proposals, not implemented client results or universal production pricing.
