[wrangler] Add schedule property to Workflow bindings for cron-based triggering

[deloreyj]

Fixes WOR-1221.

Add an optional schedule field to Workflow bindings that accepts a cron expression string or array of cron expressions. On wrangler deploy, the schedule is sent to the Workflows control plane API, enabling automatic triggering of workflow instances on a cron schedule.

NOTE: This is a configuration-only change. Scheduled triggering of Workflow instances is not yet available - adding schedule to a Workflow binding will not result in scheduled invocations at this time. This change lays the groundwork for an upcoming feature.

Changes

• Added schedule?: string | string[] to WorkflowBinding type and CfWorkflow interface
• Added validation in validateWorkflowBinding — accepts a non-empty string or non-empty array of non-empty strings; errors on wrong type, empty string, empty array, or mixed array
• Added schedule to the API payload in triggers/deploy.ts, with an error if schedule is configured on a workflow that references an external script_name (consistent with how limits is handled)

Usage

// wrangler.json
{
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "schedule": "0 9 * * 1"
    }
  ]
}

Multiple schedules:

{
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "schedule": ["0 9 * * 1", "0 17 * * 5"]
    }
  ]
}

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s): Document schedule property for Workflow bindings cloudflare-docs#29836
  • Documentation not necessary because:

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

🦋 Changeset detected

Latest commit: 7d189a6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
wrangler	Minor
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[workers-devprod]

Codeowners approval required for this PR:

• @cloudflare/wrangler

Show detailed file reviewers

• packages/workers-utils/src/config/environment.ts: [@cloudflare/wrangler]
• packages/workers-utils/src/config/validation.ts: [@cloudflare/wrangler]
• packages/workers-utils/src/worker.ts: [@cloudflare/wrangler]
• packages/workers-utils/tests/config/validation/normalize-and-validate-config.test.ts: [@cloudflare/wrangler]
• packages/wrangler/src/tests/deploy/workflows.test.ts: [@cloudflare/wrangler]
• packages/wrangler/src/dev/miniflare/index.ts: [@cloudflare/wrangler]
• packages/wrangler/src/triggers/deploy.ts: [@cloudflare/wrangler]

[github-actions]

✅ All changesets look good

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds an optional schedule field (string or string[]) to Workflow bindings, validated at config time and sent to the Workflows API on deploy. The implementation is clean and follows the existing patterns for limits well.

I found one actionable issue and posted it as a review:

1. Empty array passes validation and gets sent to the API — schedule: [] passes the .every() check vacuously, and [] is truthy in JS, so it would be serialized as { schedule: [] } in the API request. Similarly [""] passes. I posted a suggestion to add length > 0 and empty-string checks in the validation.

github run

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@13467

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@13467

miniflare

npm i https://pkg.pr.new/miniflare@13467

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@13467

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@13467

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@13467

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@13467

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@13467

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@13467

wrangler

npm i https://pkg.pr.new/wrangler@13467

commit: 3f5388a

[petebacondarwin]

Hi @deloreyj — we're doing some cleanup of stale draft PRs.

This PR has been quiet since 2026-04-16. Could you let us know within 14 days whether you're still planning to continue?

• If yes: please leave a comment with a status update or push a rebase, and we'll keep it open.
• If no: no need to reply — we'll close it after 14 days, and you can always reopen later if you pick it back up.

Thanks!

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[petebacondarwin]

I assume that workerd already implements this and that it gets picked up and works for local development in Miniflare automatically?

[workers-devprod]

Codeowners reviews satisfied