Fix one wrong number: Claude Motion edit vs a Sume Format retake
Claude Motion edits a number in place. In a Sume Format run a changed word or number means a new production; a look change is a retry at about 1/20 the cost.

When a number in the video is wrong, Claude Motion lets you change it in place: Anthropic's announcement says you can edit any word, number or timing in the editor or by asking Claude, because the animation is code. In a Sume Format run the rule is the opposite. A retry is a new take of a scene, so if the words, the host or the product change you start a new production; you retry only when the look changes.
The two products make different things, so the right fix differs. Motion makes an animation from code. A Sume Format generates footage, voice and assembly, where each scene is a generation.
Which fix applies
| What is wrong | Claude Motion | Sume Format run |
|---|---|---|
| A number or word on screen | Edit it in place | Start a new production; a retry regenerates the scene |
| Timing of one beat | Change the timing | Retry the scene with previous_run_id |
| The look of one scene | Ask Claude to redo it | Retry the scene with previous_run_id |
| The host or the product | Not applicable: no generated people | Start a new production with new scene ids |
| Need a new file | Download the MP4 again | The retry is a new run with its own id and receipt |
How a Sume retry works
Send a new POST …/runs with previous_run_id naming the run that finished. The run must be continuable: its receipt shows a thread_id that is not null, and the run completed or left artifacts. The new run has a new id, its own spend cap and its own single webhook. The original run never changes.
Bind the same output_schema on every turn, because it is per run and not inherited. Name previous_run_id, not a thread id, since a thread id returns 400 unknown_parameter.
What a retry costs
The Format cookbook says measured production retries cost approximately one twentieth of the first run's spend, and tells you to always send a cap. As an illustration only, if a first run billed $12.00, a retry of about one twentieth would be 12.00 / 20 = $0.60. The example in the docs sets the retry cap at 8, so the cap is a ceiling you choose, not a prediction.
A retry regenerates all the generative parts of that scene. It is a new take, not a re-encode, so the same instruction can produce a different picture.
Read the receipt after a retry: usage.billable_amount_usd_micros is the spend of that run alone, while artifacts[] on a continued run lists all the media the full conversation generated.
Refusals to expect
If the number that is wrong came from your data, correct the data and run again from the start. Do not ask a retry to rewrite copy that the scene was built around.
- 404 previous_run_not_found: the id is unknown or belongs to another owner.
- 400 previous_run_format_mismatch: the run started on a different Format.
- 409 previous_run_not_terminal: the run is still going; poll it and call again.
- 400 previous_run_not_resumable: there is nothing to continue, so start a new run.
Sources
Related posts
More in Formats
- Format API: webhook or polling for a run that takes 15-30 minutes
A Sume Format run returns 202 and finishes in minutes, not seconds. Take the result by signed format.run.terminal webhook or poll the run; no SSE stream.
- Spreadsheet to Format bulk queue in Node: 100-row limit and key rules
Turn a CSV of products into one bulk-runs request in Node. Items are capped at 100, concurrency at 16, and the Idempotency-Key must be new for each batch.
- Queue 100 Format runs at concurrency 16: 7 waves, one idempotency key
Sume bulk runs accept 1 to 100 items and a concurrency window of 1 to 16. The queue has no webhook, and completed does not mean all succeeded.
- Format Contents API: If-Match stops two agents overwriting each other
Per-file sha checks do not catch two agents editing different files. Send If-Match with package_sha and handle 409 format_package_sha_mismatch.
Written by Sume