// AI Platform Drift
Cloudflare Workflows adds jurisdiction restriction for data localization
Cloudflare developer changelog · published 2026-10-27 18:04 UTC
WHAT CHANGEDCloudflare Workflows now supports a jurisdiction parameter (eu, us, or fedramp) that restricts where workflow instances run and store data. The jurisdiction is set at creation and cannot be changed afterward. Wrangler 4.152.0+ is required. Deploying a Worker with a jurisdiction value that differs from an existing Workflow's jurisdiction blocks the deployment.
WHY IT MATTERSExisting Workflows have an implicit jurisdiction. If you add an explicit jurisdiction parameter to wrangler.toml that differs from what the Workflow was created with, wrangler deploy will fail and block your deployment pipeline. This affects any team with existing Workflows who adds jurisdiction configuration.
WHAT TO DOBefore adding jurisdiction parameters to wrangler.toml, verify the current jurisdiction of each existing Workflow through the Cloudflare dashboard or API. If you need a different jurisdiction, you must delete and recreate the Workflow. Upgrade to Wrangler 4.152.0 or above before using this feature.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workflows, Workers - Restrict Workflows to a jurisdiction +https://developers.cloudflare.com/changelog/post/2026-10-27-workflow-jurisdictions/ +Tue, 27 Oct 2026 00:00:00 GMT + +You can now restrict a Workflow to a jurisdiction. Its instances only run and store data within that jurisdiction, which helps you comply with data localization regulations such as GDPR ↗︎ or FedRAMP ↗︎. +Set jurisdiction on a workflows binding, or on a Workflow declared in exports: +{ +"workflows": [ +{ +"name": "my-workflow", +"binding": "MY_WORKFLOW", +"class_name": "MyWorkflow", +"jurisdiction": "eu", +}, +], +}[[workflows]] +name = "my-workflow" +binding = "MY_WORKFLOW" +class_name = "MyWorkflow" +jurisdiction = "eu" +The supported jurisdictions are eu (the European Union), us (the United States), and fedramp (FedRAMP-Moderate data centers). +A Workflow's jurisdiction is set when the Workflow is created, and cannot be changed afterwards. If an existing Workflow has a different jurisdiction, wrangler deploy and wrangler versions upload stop before uploading your Worker. +Workflow jurisdictions require Wrangler 4.152.0 or above. +For more information, refer to Data location.
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 | New data localization feature with deployment-blocking implications and version requirement. |
| signals | new feature: jurisdiction restriction on Workflows · data localization capability added · breaking change: existing Workflows with different jurisdiction block deployment · new required Wrangler version: 4.152.0+ · compliance impact: GDPR and FedRAMP support · new configuration field: jurisdiction parameter · immutable setting: jurisdiction cannot be changed after creation |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |