Workflows, Workers - Restrict Workflows to a jurisdiction

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

• 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.