Veo 3.1 previews end in 14 days: a dated checklist, Oct 8 to Oct 22
Google's three Veo 3.1 preview ids shut down on October 22, 2026. A day-by-day checklist from today, with the Sume model id and limits to test against.
You have until Thursday, October 22, 2026, which is 14 days from today (Thursday, October 8), before Google shuts down veo-3.1-generate-preview, veo-3.1-fast-generate-preview and veo-3.1-lite-generate-preview. Google's deprecations page names gemini-omni-1.1-flash as the replacement. The table below turns that into dated tasks, and uses Sume's gemini-omni-flash-1.1 row as the test target.
The calendar
The dates are working days. The goal is that the last two days are spent watching, not building.
| Date | Task | Done when |
|---|---|---|
| Thu Oct 8 | Search code, env files and CI for the three preview ids | A list of every file and caller |
| Fri Oct 9 | List monthly seconds per tier from your own logs | Seconds by Standard, Fast and Lite |
| Mon Oct 12 | Read GET /v1/videos/models; note durations and resolutions | Omni: 3 to 10 s, 360p to 4K, 16:9 and 9:16 |
| Tue Oct 13 | Run 20 real prompts through gemini-omni-flash-1.1 | 20 job ids and 20 usage.cost values |
| Wed Oct 14 | Review results with the people who approve the look | Go or no-go per use |
| Thu Oct 15 | Route 10 percent of traffic through one adapter function | No error spike for 24 hours |
| Mon Oct 19 | Raise to 100 percent; keep the old path behind a flag | Old path unused |
| Tue Oct 20 | Remove the preview ids from config and CI | Search finds no matches |
| Wed Oct 21 | Archive finished clips you still need | Files stored in your own storage |
| Thu Oct 22 | Shutdown day: confirm nothing calls a preview id | Zero calls in logs |
What to check against the Sume row
Sume's docs list gemini-omni-flash-1.1 at 3 to 10 seconds, 360p, 720p, 1080p and 4K, in 16:9 or 9:16, with native synced audio that is always on. It accepts image references (up to 10) and video references (up to 3 clips of 3 seconds). Sume bills the provider list times 1.25 per output second, so 8 seconds at 720p is 8 x $0.125 = $1.00 and at 1080p is 8 x $0.1875 = $1.50.
- If a caller asked for a length outside 3 to 10 seconds, clamp it or split it.
- If a caller needs Veo's extension, Omni's docs describe their own: continuations of 3 to 10 seconds up to 40 seconds in total.
- If a caller sent a seed, Sume rejects
seed; remove it. - If a caller turned audio off, the Sume row keeps audio on and rejects
generate_audio: false.
Keep the swap reversible until the end
Put the model id and the base URL in configuration. Send an Idempotency-Key on each submit so a retry returns the original job. Log the job id, the model id and usage.cost for every clip, so that on October 22 you can show which path produced which file. Sume does not list a Veo model, so the old path can only be a Google call; once Google's preview ids end, that path is dead, and the flag only protects the days before.
Who should own each task
Split the list by owner so nothing waits on a meeting. An engineer owns the search and the adapter. Whoever pays the bill owns the monthly-seconds count, because the cost question is simple multiplication: seconds per month times the per-second rate. For example 500 seconds a month at 720p on Sume is 500 x $0.125 = $62.50. Whoever approves creative owns the Wednesday review, and should bring the same 20 prompts the engineer ran, so the comparison is fair. If the review fails for a use, note which model feature it needed, and check the Sume catalog for another row before October 22.
After the date
On October 23, search your logs for any request that returned a not-found style error from Google and fix the caller that still held a preview id. Then re-read the Google deprecations page: if it adds a new date or id, the checklist above is the template for the next one.
Sources
Related posts
More in Developers
- Vercel 800 s max duration: do you still need a Sume webhook?
Vercel Pro allows 800 s functions and a 30-minute beta. A Sume video job can still outlast one request, so use async or webhook mode and return in seconds.
- Vercel's 300 s default: does a 30 s Sume image sync call fit?
Yes: with fluid compute the default is 300 seconds, far above the 30-second Sume image wait. Branch on 200, 202 and 502, and poll video jobs instead.
- Verify a Sume Format webhook in Python: empty secret, stale timestamp
A Python check for the Sume format.run.terminal webhook: HMAC-SHA256 over timestamp.raw_body, a 5-minute window, and a refusal to run with an empty secret.
- Verify a Sume avatar video webhook signature in Python
A Python verifier for Sume job webhooks: HMAC SHA-256 over timestamp.raw_body, sume-v1 entries, a 5-minute window, and a refusal when the secret is empty.
Written by Sume