Whether a published retirement date can move
It depends on who published it. One platform states that retirement dates are not extendable, so a date can only arrive. One maker describes its dates as the earliest on which a model might be retired, so each one is a floor that can quietly become later. Two rows that look alike. From 4 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.
| Entry | What is published | Detail |
|---|---|---|
| Microsoft Foundry | Dates are stated to be non-extendable | No exception route is described |
| Gemini API | Dates are the earliest a model might go | A floor, so it can become later |
| Amazon Bedrock | A period, plus a date before which nothing ends | The floor is published, not the day |
| LTX Studio | No dates at all, and a right to replace | Nothing to be early or late against |
| Every other entry | Nothing published | No date in either direction |
Inclusion rule. Filled from a published sentence about whether a date can change. An observation that a date was met, or missed, is not a published statement. Order. Fixed dates first, then floors, then entries with no date.
1Fixed and soft dates support different plans
A fixed date goes into a calendar and gets communicated to clients. A floor supports a migration prepared and then held, possibly for a long time, at the cost of storage and attention rather than a re-done season.
Reading both as the same kind of commitment plans two migrations wrong. The wording is therefore worth keeping verbatim rather than summarising as a shutdown date.
2Refusing extensions is the more plannable position
Most enterprise documents leave room for an exception, on the assumption a large customer will ask. Stating plainly that dates do not move removes an input that was never reliable.
It reads as unhelpful. A production that knows the day is fixed can schedule the work instead of carrying it as an open worry.
3A soft date leaves no record of slipping
If a model keeps answering past its listed date, no correction is published and the row may simply remain. So a reader cannot tell whether a date slipped or whether their own check was wrong.
That makes the table honest and unusable as a record of what happened. The wording is the fact, and the number is a lower bound.
- Whether a date can be pushed back on requestRetirement dates are not extendable
- What a date in that table commits toThe shutdown dates listed indicate the earliest possible dates on which a model might be retired
- Legacy periodSix months or 45 days, stated on each model cardwhich is the notice given before end-of-life
- Published noticeThe pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind here
4A pipeline across model versions
Model end dates touch “Can a date move”; SceneMixer's guides describe how its pipeline treats the models it runs:
Wan 3.0 is Alibaba Cloud's video generation model on the Model Studio platform, called through an asynchronous submit-then-poll API, in two tiers: the standard wan3.0-video and the faster wan3.0-video-prime.
SceneMixer, Wan 3.0 for AI Short Drama (2026): Parameters, Reference Limits, Moderation Rules and the 30-Second Take (read 2026-10-13)
A script is read once per project; switching affects later tasks such as a storyboard.
SceneMixer, Doubao Seed 2.1 Pro — “Does Pro re-read my script?” (read 2026-10-13)
5Sources
Dates come from the company that makes the model or the platform that serves it; menus come from the app, and both are linked on the calendar. Read 2026-09-22. What counts as a date is on sourcing. Nearby: Cut off early, Who moves you, Published states.