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. ›Workers
  4. ›Update

Feature•Jun 2, 2026

Schedule Workflow instances directly from your Workflow binding

WorkersCloudflare · Developer platform

You can now attach cron schedules directly to a Workflow binding in wrangler.jsonc. Each scheduled run creates a new Workflow instance automatically, so you do not need to define a separate Worker with a scheduled handler just to trigger your Workflow on an interval.

For example, you can configure hourly, every-15-minute, or weekday schedules on the same Workflow:

{ "workflows": [ { "name": "my-scheduled-workflow", "binding": "MY_WORKFLOW", "class_name": "MyScheduledWorkflow", "schedules": ["0 * * * *", "*/15 * * * *", "0 9 * * MON-FRI"], }, ], }

Cron workloads get all the same benefits of Workflows with built-in retries, multi-step durable execution, and configurable timeouts of Workflows.

import { WorkflowEntrypoint, WorkflowEvent, WorkflowStep, } from "cloudflare:workers"; // Runs automatically on each cron schedule defined for the MY_WORKFLOW binding in wrangler.jsonc. export class MyScheduledWorkflow extends WorkflowEntrypoint<Env> { async run(event: WorkflowEvent, step: WorkflowStep) { const data = await step.do("fetch source data", async () => { return await fetchSourceData(); }); // If this step fails, only this step is retried with the custom logic below await step.do( "process and store results", { retries: { limit: 5, delay: "30 seconds", backoff: "exponential" }, timeout: "10 minutes", }, async () => { await processAndStore(data); }, ); } }

This makes it easier to build recurring, scheduled jobs such as database backups, invoice generation, report aggregation, and cleanup tasks without wiring up a separate Cron Trigger entrypoint.

For more information, refer to Trigger Workflows.

Read the original announcement↗

More from Workers

All Workers updates →
  1. Workers subrequests now preserve context for BYOIP destinations

    Cloudflare now preserves Workers context when a subrequest targets a Cloudflare-proxied hostname using Bring Your Own IP (BYOIP). These requests are identified as Cloudflare-to-Cloudflare traffic instead of external Internet traffic.

    Workers•Feature•Oct 13, 2026
  2. Cloudflare API MCP server sends Workers Issues as MCP Events

    Workers Issues provides built-in error monitoring for Cloudflare Workers. It detects production failures and groups related failures into issues without an SDK or application wrapper.

    Workers•Feature•Oct 13, 2026
  3. Workers Builds now posts preview URLs in seconds

    Workers Builds now consistently posts preview URLs to GitHub pull requests and GitLab merge requests within a few seconds of a build completing, so you can start testing and reviewing your changes sooner. Previously, posting preview URLs could often take minutes.

    Workers•Preview•Oct 12, 2026
  4. More time for requests to finish during Workers runtime updates

    Pending requests and connections to Workers now have a grace period of up to 20 minutes during Workers runtime updates. Previously, the grace period was up to 30 seconds.

    Workers•Feature•Oct 12, 2026
  5. Run OpenCode 2.0 on Cloudflare with the Agents SDK

    The Agents SDK now supports OpenCode 2.0 through the experimental OpenCodeHarness. Run OpenCode inside a plain Durable Object, with sessions stored in SQLite and Lifecycle jobs that wake interrupted work after eviction.

    Workers•Feature•Oct 12, 2026