gen3a_turbo no longer available on Runway: re-read Sume's model list

Runway's changelog says gen3a_turbo and gen4_aleph are no longer available and requests using them fail. On Sume, avoid that failure mode by reading GET /v1/videos/models at startup and choosing an id from the response, rather than baking an id into your code.

Sources: the Runway Dev changelog (July 30, 2026) and Sume's video generation docs, read 2026-10-01.

What did Runway remove?

The entry says Gen-3 Alpha Turbo (gen3a_turbo) and Gen-4 Aleph (gen4_aleph) are no longer available on Runway Dev. It points Gen-3 Alpha Turbo users to Gen-4.5 or Gen-4 Turbo, and Gen-4 Aleph users to Aleph 2.0 (aleph2).

How does Sume's list change?

The docs say some catalog models are listed only when their provider is configured, and that limits are per model: seedance-2.5 accepts 4–30 seconds while most other catalog models top out at 15 seconds (wan-3.0 accepts 2–30). So the set of valid ids and ranges is data, not a constant.

What should my client do?

Fetch the list, cache it briefly, and validate the chosen id, duration and resolution against the entry before submitting. For an earlier retirement on Sume, see Kling 2.1 sunset.

const res = await fetch("https://api.sume.com/v1/videos/models", {
  headers: { Authorization: "Bearer " + process.env.SUME_API_KEY },
});
console.log(await res.json());

What happens to a job that fails?

The generation docs say failed jobs and failed queue admission release or refund the reservation where applicable. Resubmitting with a valid id is a new request.