Tools2 min read

Cloudflare will retire selected Workers AI models on November 20

Cloudflare moved selected Workers AI model retirements from November 15 to 20. Check exact IDs, replacement access and customer-facing workflows.

Prepared by the NADALI editorial team using AI

Conceptual AI illustration: two glowing routes lead from one node to a closed gate and a processor block; not the Cloudflare interface.
Nadali editorial illustration created with OpenAI gpt-image-2-2026-04-21; reused from Nadali's Gemini API migration article. · Original AI-generated editorial illustration created for Nadali; use subject to applicable OpenAI terms; no exclusive copyright claim; no third-party input images used. · 1440 × 960

Author: Nadali. Prepared using AI.

Cloudflare moved the retirement of selected Workers AI models from November 15 to November 20, 2026. The announcement is dated November 5; this is the current deadline checked by Nadali on November 10.

Who should act

Teams whose chatbots, search or file processing use the listed models. Hosting a website on Cloudflare does not by itself establish that dependency. Examples include @cf/zai-org/glm-5.2, @cf/openai/whisper-tiny-en and @cf/google/embeddinggemma-300m. Consult the announcement for the full list.

The errors documentation says requests to a retired model return HTTP 410 and internal code 5028. Our editorial takeaway: repeatedly retrying that request is not a customer-service recovery plan.

Check the replacement separately

The suggested replacement for embeddinggemma-300m, embeddinggemma-2, is still marked as forthcoming in the announcement. Do not plan a migration solely around its mention.

One recommended option for text tasks, DeepSeek V4.1 Flash 1017, requires Workers Paid or prepaid AI Gateway credits. Standard Workers Free billing is insufficient. Pricing varies by model and operation type; switching does not guarantee the same cost.

What to ask your developer

Nadali’s editorial checklist before approving a migration:

  1. Which exact model IDs do production and fallback workflows use? Compare them with the full list, rather than provider names alone.
  2. Is the chosen replacement available in the account, within the approved budget and compatible with your data requirements?
  3. Does it pass the same verified examples: Ukrainian language, response format, tool calls and waiting time?
  4. How will the team handle enquiries manually if the AI workflow stops? Who will confirm migration completion before November 20?

Keep the trial results and responsible person in one record. Changing the model name in settings alone is not enough to accept the work.

Nadali has not checked a specific account, made API calls or tested replacement compatibility. Sources were read on November 10, 2026. Cover: a reused conceptual Nadali AI illustration of a route change, not the Cloudflare interface. 

Sources and verification

  1. Cloudflare: Planned model deprecations on Workers AI, November 5, 2026 ↗
    Source checked: 2026-11-10
  2. Cloudflare Workers AI: Errors ↗
    Source checked: 2026-11-10
  3. Cloudflare Workers AI: DeepSeek V4.1 Flash 1017 access and parameters ↗
    Source checked: 2026-11-10
  4. Cloudflare Workers AI: Pricing ↗
    Source checked: 2026-11-10