jobs_wait any on 20 Wan 3.0 clips: the other 19 still bill $5.94

If an agent submits 20 Wan 3.0 clips of 5 seconds at 480p and then calls jobs_wait with wait_for: "any", the call can return when the first clip ends, while the other 19 keep running and billing: $5.9375 of the $6.25 batch. The docs say it plainly: the remaining jobs continue and still bill.

What the batch costs

Wan 3.0 480p is $0.0625 per second, so one 5-second clip is $0.3125. jobs_wait takes 1 to 20 job_ids.

The wait call

Use wait_for: "all" (the default) when you need every clip, and any only when you will use the first result and cancel the rest. A cancel works only before generation starts.

{
  "job_ids": ["job_a", "job_b", "job_c"],
  "wait_for": "all",
  "timeout_seconds": 50,
  "include_results": true
}

Limits and gotchas

A single call holds at most 55 seconds (default 50). On wait_slice_expired, repeat the call with the same ids and never resubmit the paid create.

• jobs_cancel needs the Write scope and an idempotency_key.
• A 524, 522, 523 or 525 on the wait is a transport failure, not a job outcome.
• One unknown or foreign-workspace id fails the whole call.