CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Workflows
  4. ›Update

Feature•Oct 8, 2026

Create Workflow instance batches by count or list

WorkflowsCloudflare · Developer platform

createBatch() now accepts an options object that creates up to 100 Workflow instances in one call. The result lists the created instances and explains why any others were not created. To use this form in local development and get its types from wrangler types, use Wrangler 4.148.0 or later.

To create instances that share the same options, pass count. Each instance receives a generated ID:

const result = await env.MY_WORKFLOW.createBatch({ count: 10, params: { report: "daily" }, });

const result = await env.MY_WORKFLOW.createBatch({ count: 10, params: { report: "daily" }, });

To give each instance its own ID or options, pass instances:

const { created, errors } = await env.MY_WORKFLOW.createBatch({ instances: [ { id: "order-1", params: { orderId: 1 } }, { id: "order-2", params: { orderId: 2 } }, ], }); for (const error of errors) { console.log(error.index, error.id, error.code, error.message); }

const { created, errors } = await env.MY_WORKFLOW.createBatch({ instances: [ { id: "order-1", params: { orderId: 1 } }, { id: "order-2", params: { orderId: 2 } }, ], }); for (const error of errors) { console.log(error.index, error.id, error.code, error.message); }

created contains the created instances. errors contains each entry that was not created, identified by its position in the input. IDs that already exist and IDs repeated within the batch are reported as errors instead of being skipped silently.

Passing an array to createBatch() is deprecated. Existing code that uses the array form continues to work.

For more information, refer to createBatch.

Read the original announcement↗

More from Workflows

All Workflows updates →
  1. Call Workflows declared in `exports` through `ctx.exports`

    A Worker can now call the Workflows it declares in the exports field of its Wrangler configuration through ctx.exports. You no longer need a workflows binding to call a Workflow from the Worker that defines it.

    Workflows•Feature•Sep 27, 2026
  2. 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.

    Workflows•Feature•Sep 24, 2026
  3. Delete Workflow instances individually or in batches

    You can now delete one or up to 100 Workflow instances and their stored state via the Workflows API or Wrangler 4.125.0 and later. Deleting an instance frees its stored state and stops its current execution. Storage billing is based on the average daily peak.

    Workflows•Feature•Sep 17, 2026
  4. Stream Workflow instance events in your Worker or via the API with.subscribe()

    You can now stream Workflow instance events via WorkflowInstance.subscribe() and the GET /subscribe API endpoint. Workers and HTTP clients can react to workflow and step events, including attempts, sleeps, waits, and rollbacks, without polling for instance status.

    Workflows•Feature•Sep 15, 2026
  5. Default instance retention for new Workflows on Workers Paid is seven days

    Workflows created on or after September 10, 2026, on the Workers Paid plan retain completed and errored instance state for seven days by default (previously 30 days). The seven day default helps to reduce storage costs by default. The maximum retention limit remains 30 days.

    Workflows•Feature•Sep 10, 2026