When a take fails#
Applies to v0.14Last reviewed
In short
When a generation produces nothing, the card in CODA says so in plain words, and you are not charged for a take that failed, with two rare exceptions where the card's own sentence says what it cost. It also says whether trying again can help.
Sometimes a generation does not produce anything. When that happens the card in CODA says so in plain words, and you are not charged for a take that failed — with two rare exceptions, where the card's own sentence says what it cost (below).
What the card says#
The card turns into a short notice with a heading and one sentence:
- This take did not start. The request never reached the point of making anything. Either the generation service could not be reached — the card adds Trying again may work — or it turned the request down.
- This take failed. The request was accepted and then could not be finished.
Under the sentence the card may say whether trying again can help: Trying again may work, or Trying again will not help — this needs fixing first. When it says neither, the failure did not tell us, and we do not guess.
Two failures can still have cost something, and their sentence says so rather than Nothing was charged: a request that may have reached the generation service with no answer back (its cost is held until we have checked), and a take that finished but whose result was gone before we could collect it (charged at its quoted price, or held until we have checked). A take you cancelled is headed This take was cancelled — it is not a failure; see Cancelling a take.
The last line is a short code, such as provider_submit_failed. A take whose inputs the generation service refused before starting (for example, a start frame it could not use) is headed This take did not start, says which input it refused, and has the code provider_rejected_input: nothing is charged, and it is not retried on its own, because the same inputs would be refused again. A take the service accepted and then could not finish fails with provider_error, also with nothing charged; ask CODA to make it again. If you contact support,
quote it: it tells us exactly which kind of failure this was, and the full details are already
in our logs.
In an autopilot run#
A run's step that fails shows the same kind of sentence under the step, with its code in brackets. Some steps are stopped before anything is generated — for example because a shot has been deleted, or the run's approver no longer has access — and the sentence says which. Nothing is spent on a step that never started.
When a click is refused before anything starts#
A click on a card can be refused before a take exists, for a reason you can act on: the picture a clip starts from has not been checked yet, a character on the shot is still being prepared, the production has reached its spending for the day, or the card was closed. The answer says which, in plain words, with what to do first, and that nothing was charged. A card that would be refused says so before you click, and its note goes away on its own when the cause does.
Ask CODA what went wrong. The app keeps a short record of what was refused or failed for you in the last thirty days, in the same words you were shown, and CODA reads it whenever you talk to her. Ask "why didn't my clip start?" or "there is an error, can you check?" and she says what is on record and what to do about it, with a link to the place; if she has no record of an error she says so and asks what you saw and where, instead of guessing. She never tells you a code, a model or a provider's name. When the same thing keeps happening she says so, and offers the real fix, not another try.
CODA knows about more than a refused click. A take or a run step that failed, a change the app would not save, a delete, a lock or an upload that was refused, a connection that dropped part-way, and a panel that stopped working and was reset are all on the same record, each with what it means, the usual causes and what you can do. If a failure needs the person who runs the system, CODA says so and tells you what to pass on: what you were doing, and when.
What to do#
- If the card says Trying again may work, wait a moment and send the proposal again.
- If it says Trying again will not help, the problem is on our side or in the request itself; sending it again gives the same result. Contact support with the code.
- If a run's step names something you can change — a shot, a reference, a prompt — change it and ask CODA for a new plan.