Replicate aborted vs canceled prediction: Sume cancel and 409

On Replicate, a deadline hit before a prediction starts gives aborted and no charge; after it starts, canceled and you pay for run time. Sume has no aborted status. A cancel works only before generation starts; after that it returns 409 job_generation_already_started.

Replicate facts come from its prediction lifecycle page; Sume facts from Generation admission, Jobs and results and Errors and credits, read 2026-10-01.

How does Replicate split aborted from canceled?

The lifecycle page defines canceled as canceled by the user or past its deadline after starting, and aborted as past its deadline before it could start. Billing follows: aborted, never started, no charge; canceled, started, you pay for the time it ran. Predictions also time out after 30 minutes.

What does Sume do at the start boundary?

Cancellation succeeds only before generation work starts. Once generation has started the API returns 409 job_generation_already_started with details.cancelable: false, and the job completes or fails normally. Cancelling a job already canceled is idempotent and returns the same canceled job.

Which Sume statuses exist?

Job status values are queued, processing, completed, failed, canceled. The 409 family covers job_not_completed, job_not_cancelable and job_generation_already_started, each meaning the operation is not valid for the current status.

What should I do to avoid a started job I do not want?

Cancel queued jobs you no longer need before they start processing, since there is no cancel after that. These pages do not cover how a started job is billed, so read the billing docs before relying on a cost assumption. A local timeout is not a reason to submit again; see cancel AI video jobs and runs.