Workflows, Workers - Declare Workflows in the exports configuration
Cloudflare Workflows changelog published Workflows, Workers - Declare Workflows in the exports configuration. You can now declare the Workflows a Worker defines in the exports field of your Wrangler configuration file. Previously, a Worker could only define a Workflow through a workflows binding, even when the Worker never called the Workflow itself. Key…
Why this signal matters
Cloudflare Workflows changelog published Workflows, Workers - Declare Workflows in the exports configuration. 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 declare the Workflows a Worker defines in the exports field of your Wrangler configuration file. Previously, a Worker could only define a Workflow through a workflows binding, even when the Worker never called the Workflow itself. Key each entry by the name of the class that extends WorkflowEntrypoint : { "exports" : { "MyWorkflow" : { "type" : "workflow" , "name" : "my-workflow" , "limits" : { "steps" : 25000 , }, "schedules" : "0 " , }, }, } exports . MyWorkflow type = "workflow" name = "my-workflow" schedules = "0 " exports . MyWorkflow . limits steps = 25 000 </pre
Actionable summary
Treat Workflows, Workers - Declare Workflows in the exports configuration as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.
- Agent usefulness
- 75/100
- Confidence
- 90%
- Canonical data
- JSON + Markdown
What builders should check
- 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.