// AI Platform Drift
Cloudflare blocks dispatch namespace renames via API and CLI
Cloudflare developer changelog · published 2026-11-21 07:10 UTC
WHAT CHANGEDPUT and PATCH requests to the dispatch namespace API now return a 400 error with code 100413 if they attempt to change the name field. The wrangler dispatch-namespace rename command and Terraform cloudflare_workers_for_platforms_dispatch_namespace resource name changes fail with the same error. Cloudflare states this prevents failures where dispatch Workers and outbound Workers retained the old namespace name after a rename, causing subsequent API requests to read, deploy, or delete Workers to fail.
WHY IT MATTERSAny automation or infrastructure-as-code that renames dispatch namespaces will break. Terraform applies that change the name attribute will fail. Existing runbooks or scripts that use wrangler dispatch-namespace rename will stop working.
WHAT TO DOAudit your Terraform configurations, CI/CD pipelines, and operational scripts for dispatch namespace renames. Replace rename operations with the documented five-step migration: create new namespace, deploy user Workers to it, update dispatch Worker binding, verify routing, delete old namespace. Update any runbooks that reference wrangler dispatch-namespace rename.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers for Platforms - Dispatch namespaces can no longer be renamed +https://developers.cloudflare.com/changelog/post/2026-11-20-dispatch-namespace-rename-removed/ +Fri, 20 Nov 2026 00:00:00 GMT + +You can no longer rename a dispatch namespace after creating it. +Renaming a namespace could cause API requests to read, deploy, or delete Workers to fail because dispatch Workers and outbound Workers retained the namespace name they were deployed with. This change prevents those failures by rejecting rename requests. +What changes: + +PUT and PATCH requests to the dispatch namespace API return a 400 error with code 100413 if they change name: +Dispatch namespaces cannot be renamed. The name in the request must match the namespace's current name. To use a different name, create a new dispatch namespace. + +wrangler dispatch-namespace rename returns the same 100413 error. + +Terraform applies that attempt to change name on a cloudflare_workers_for_platforms_dispatch_namespace resource fail. + +To move your Workers to a namespace with a different name: + +Create a new dispatch namespace with the name you want. +Deploy your user Workers to the new namespace. +Update the dispatch namespace binding in your dispatch Worker to reference the new namespace, then redeploy the dispatch Worker. +Verify that requests are routed to the new namespace and your Workers work as expected. +Delete the user Workers in the old namespace, then delete the old namespace. + +For more information, refer to How Workers for Platforms works.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.95, needed 0.5 |
|---|---|
| triage reasoning | Breaking API change removes rename capability; requires code and deployment changes. |
| signals | breaking API change: PUT/PATCH requests now return 400 error · CLI tool behavior change: wrangler dispatch-namespace rename now fails · infrastructure-as-code impact: Terraform cloudflare_workers_for_platforms_dispatch_namespace resource affected · operational procedure required: multi-step workaround documented for namespace migration · error code introduced: 100413 |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |