Runway SAFETY.INPUT credits not refunded: what Sume does

Runway's task-failure page says that, unlike other failures, credits are not refunded for SAFETY.INPUT.* failures, and that you should not retry them. Sume's docs state a single rule instead: a failed job releases or refunds its reservation, and the usage ledger shows it as refunded. The pages I read do not mention content-moderation failures or any exception for them.

Runway text read 2026-10-01 from its Dev docs; Sume text from the docs pages listed under sources, same date. This is not legal or financial advice, and your own invoice is the record.

What does Runway's page say?

Failure codes starting with SAFETY. mean content moderation rejected the task, on inputs or outputs. For SAFETY.INPUT.* the credit is not refunded. The page also calls the last part of the code diagnostic only and says not to expose it to users.

What do Sume's docs say about failed jobs?

Sume reserves the estimated amount when it accepts a request, captures it on success, and refunds on failure or cancellation before capture. Failed jobs and failed queue admission release or refund the reservation "where applicable".

Are there cases where a failed run still costs money?

For multi-step Format runs, yes. The Formats errors page says generation that finished before a cancel or a failure is billed, and a later step failing does not refund it. A 4xx at create costs nothing. See the Formats errors page.

How do I confirm what I was charged?

Read GET /v1/usage and match the job id or request id to the row status: reserved, captured or refunded. The usage docs describe each. For more on failed generations, see AI video generator refund policy.