Cloud Tasks batch delete GA: a deleted task is not a canceled Sume job

Deleting Cloud Tasks tasks does not cancel Sume jobs: a deleted task is a submit that never ran, while a job Sume already accepted keeps going until you call POST /v1/jobs/{job_id}/cancel, and that call succeeds only before generation work starts. Google announced on 2026-09-30 that batch task creation, batch task deletion and task-level retry configuration are generally available in the v2 and v2beta3 APIs.

The Google detail is from the Cloud Tasks release notes, read 2026-10-03; Sume's cancel rule is from Jobs and results and Generation admission. I did not run a Cloud Tasks queue against Sume.

How do I abort a wave in the right order?

Delete first, so no new submits start, then cancel the jobs your handlers already created. Your handlers must have stored each job_id at submit time for the second step to work. A task that ran between your listing and your delete has already created its job, so the cancel pass must read your store after the delete, not before.

What does cancel do once the job has started?

Sume answers 409 job_generation_already_started with details.cancelable: false, and the job runs to completion and bills. Cancelling a job that is already canceled is idempotent and returns the same canceled job. Queued jobs you no longer need are the ones worth canceling, and canceling them is also the recommended response to 429 queue_full.

Do not treat a failed cancel as a reason to submit again. Poll status_url to the terminal state and use the result or drop it.