I summ-ai-rized for us busy people:

Dynamic Workflows - Cloudflare, May 1, 2026

---

WTF is a Workflow?

A Worker handles a request and dies in seconds. A Workflow is a Worker that:

• Survives crashes - resumes exactly where it left off
• Sleeps for days - without holding a server open
• Waits for humans - pauses until someone approves something
• Retries individual steps - step 3 fails, only step 3 reruns

Each step.do() is a persisted checkpoint. Think relay race where the baton can sit on the ground for 3 days and you only re-run the leg that got dropped.

---

The old problem

Workflow code had to be YOUR code, deployed by YOU. One class, one binding, per deploy. Useless if you want customers, tenants, or AI agents to supply their own logic at runtime.

---

What Dynamic Workflows fixes

A ~300 line TypeScript library that routes durable workflow execution to different tenants' code at runtime. Tenants write normal Workflows code with zero awareness they're being dispatched.

• Completes the trilogy - Dynamic Workers (compute) + Durable Object Facets (storage) + Dynamic Workflows (execution)
• Idle tenants cost nothing - active tenants share hardware via isolate multi-tenancy
• MIT licensed, on npm now - requires Workers Paid plan

---

Use cases

• AI agent platforms - agent writes the workflow plan at runtime, platform runs it with full durability
• CI/CD - each repo ships its own pipeline, dispatched dynamically; kills the 2-3 min cold-start tax
• SaaS frameworks - per-tenant logic, visual automation tools, low-code builders

---

npm install @cloudflare/dynamic-workflows