cancel-in-progress killed my workflow; does the Sume job stop?

No: cancelling a GitHub Actions run does not cancel the Sume job it submitted. The Sume docs say a client-side timeout does not cancel a job, and an explicit POST /v1/jobs/{job_id}/cancel succeeds only before generation work starts.

Sume behavior is from the Jobs and results docs; the GitHub concurrency text was read 2026-09-30.

What does cancel-in-progress do?

GitHub's concurrency page says setting cancel-in-progress: true will “also cancel any currently running job or workflow in the same concurrency group.” It stops the runner. It does not know about a request you already sent to another service.

How do I cancel the job myself?

Call the cancel endpoint with the job id you saved from the submit response. Cancelling a job that is already canceled is idempotent and returns the same canceled job.

curl -X POST https://api.sume.com/v1/jobs/job_123/cancel \
  -H "Authorization: Bearer $SUME_API_KEY"

What does the 409 mean?

It means generation has already started. The response carries details.cancelable: false and the job runs to completion, so do not resubmit it; read the result once it is terminal.

How do I avoid orphaned jobs on a superseded run?

Write the job id to an artifact or a store as soon as the submit returns. The next run in the group can then look up the earlier job by id and read its status instead of submitting new paid work.