Cloudflare now rejects any attempt to change the name of an existing dispatch namespace after it has been created.
This change matters because API calls, CLI commands, and IaC tools that previously allowed a rename will now return a 400 error (code 100413), breaking automation pipelines and potentially causing deployment failures.
What the API Enforces
PUTandPATCHto the dispatch namespace endpoint must keep thenamefield unchanged; a mismatch triggers a 400 response with error code 100413.- The
wrangler dispatch-namespace renamecommand surfaces the same error. - Terraform resources of type
cloudflare_workers_for_platforms_dispatch_namespacethat attempt to modifynamewill cause the apply step to fail.
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.
Why Engineers Should Care
Renaming was a convenient way to correct naming mistakes or align with evolving service contracts. With the new restriction, any script, CI/CD job, or Terraform plan that includes a name change will abort, leading to stalled releases or manual intervention. The error also prevents silent mismatches that could cause runtime failures when Workers reference a namespace that no longer matches their deployment metadata.
Migration Path
- Create a fresh dispatch namespace using the desired identifier.
- Deploy all user Workers to the new namespace.
- Update the dispatch‑worker binding to point at the new namespace and redeploy the dispatch Worker.
- Confirm that traffic is correctly routed to the new namespace and that Workers behave as expected.
- Remove the old Workers and delete the original namespace.
Each step should be reflected in version‑controlled configuration so that Terraform state stays consistent and CI pipelines can verify the transition.
Operational Considerations
Teams should audit existing IaC for any name changes and lock those resources to prevent_destroy = false only after the migration is complete. Monitoring for 400/100413 responses can surface stray rename attempts in logs. Because the rename guard also applies to outbound Workers that embed the namespace name, ensuring all bindings are updated eliminates a class of routing errors.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
Treat dispatch namespace names as immutable identifiers. Incorporate the creation‑only model into design reviews, update automation to avoid rename operations, and plan a one‑time migration if a name change is required. Doing so preserves pipeline stability and prevents unexpected request failures.
