Workflows

You can now use @cloudflare/dynamic-workflows to run a Workflow inside a Dynamic Worker, ensuring durable execution for code that is loaded at runtime. The Worker Loader loads Dynamic Workers on demand, which previously made durability challenging. Even within a Dynamic…

Workflows now provides additional context inside step.do() callbacks and supports returning ReadableStream to handle larger step outputs. Step context properties The step.do() callback receives a context object with new properties alongside attempt: step.name — The name passed to step.do() step.count…

Workflows limits have been raised to the following: LimitPreviousNewConcurrent instances (running in parallel)10,00050,000Instance creation rate (per account)100/second per account300/second per account, 100/second per workflowQueued instances per Workflow 11 million2 million These increases apply to all users on the Workers Paid…

All wrangler workflows commands now accept a --local flag to target a Workflow running in a local wrangler dev session instead of the production API. You can now manage the full Workflow lifecycle locally, including triggering Workflows, listing instances, pausing,…

Workflow instance methods pause(), resume(), restart(), and terminate() are now available in local development when using wrangler dev. You can now test the full Workflow instance lifecycle locally: const instance = await env.MY_WORKFLOW.create({ id: "my-instance-id",}); await instance.pause(); // pauses a…

Cloudflare Workflows allows you to configure specific retry logic for each step in your workflow execution. Now, you can access which retry attempt is currently executing for calls to step.do(): await step.do("my-step", async (ctx) => { // ctx.attempt is 1…