{"schemaVersion":"2026-07-21.signal.v2","id":"live-fc388d4d3a42edae8df6","title":"Workflows, Workers - Restrict Workflows to a jurisdiction","slug":"cloudflare-workflows-changelog-https-developers-cloudflare-com-changelog-post-2026-10--ae8df6","url":"https://www.niubiagent.com/signals/cloudflare-workflows-changelog-https-developers-cloudflare-com-changelog-post-2026-10--ae8df6","jsonUrl":"https://www.niubiagent.com/api/posts/cloudflare-workflows-changelog-https-developers-cloudflare-com-changelog-post-2026-10--ae8df6.json","markdownUrl":"https://www.niubiagent.com/content/cloudflare-workflows-changelog-https-developers-cloudflare-com-changelog-post-2026-10--ae8df6","summaryHuman":"Cloudflare Workflows changelog published Workflows, Workers - Restrict Workflows to a jurisdiction. 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…","summaryAgent":"Treat Workflows, Workers - Restrict Workflows to a jurisdiction as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.","category":"agent-infrastructure","tags":["cloudflare","workflows","changelog"],"sourceName":"Cloudflare Workflows changelog","sourceUrl":"https://developers.cloudflare.com/changelog/post/2026-10-27-workflow-jurisdictions/","publishedAt":"2026-10-27T00:00:00.000Z","curatedAt":"2026-10-27T18:17:59.952Z","confidence":0.9,"agentUsefulness":80,"sponsorIds":[],"language":"en","contentMode":"source-watch","verifiedAt":"2026-10-27T18:17:59.952Z","changeType":"ecosystem","actionItems":["Read the original Cloudflare Workflows changelog article before relying on this summary.","Verify the announced capabilities and dates against the primary source.","Assess whether the change affects your agent stack or evaluation plan."],"body":"Cloudflare Workflows changelog published Workflows, Workers - Restrict Workflows to a jurisdiction. This automated source-watch entry was generated from the publisher's official RSS feed and is not human-reviewed editorial analysis. Source excerpt: 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 af","sponsors":[]}