triggers error messages not displaying

[mike-git374]

What versions & operating system are you using?

System:
    OS: Linux 7.0 Fedora Linux 44 (Container Image)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12600K
    Memory: 81.53 GB / 94.05 GB
    Container: Yes
    Shell: 5.3.9 - /bin/bash
  Binaries:
    Node: 26.1.0 - /root/.local/share/pnpm/bin/node
    pnpm: 11.5.2 - /root/.local/share/pnpm/bin/pnpm

Please provide a link to a minimal reproduction

todo

Describe the Bug

[ERROR] Some triggers failed to deploy for myWorker

The AI helper said it might be because the top level "name" field does not match the workflow "name" field, as all documentation and examples have those matching, but I don't know why the worker name has to match the workflow name. Deploys fine except trigger doesn't work. If I remove the "schedules" field no error

{
	"name": "myWorker",
	"main": "worker.mjs",
	"workflows": [{
		"name": "WF_name",
		"binding": "WF_name",
		"class_name": "WF_name",
		"schedules": [ "*/5 * * * *" ],
	}],
	"compatibility_date": "2026-06-13",
}

Please provide any relevant error logs

[ERROR] Some triggers failed to deploy for myWorker

A request to the Cloudflare API
(/accounts/ID/workflows/WF_name) failed

[tsushanth]

The schedules field doesn't belong inside the workflows[] binding — wrangler's WorkflowBinding type only accepts binding, name, class_name, optional script_name, optional remote, and an optional limits.steps. There's no per-workflow schedule field in the wrangler config today; the schedules: [...] you have is being passed through verbatim to the API, which then rejects the request — that's the [ERROR] Some triggers failed to deploy you're seeing.

For Workers Cron Triggers, the field is triggers.crons at the top level:

{
  "name": "myWorker",
  "main": "worker.mjs",
  "triggers": {
    "crons": ["*/5 * * * *"]
  },
  "workflows": [{
    "name": "WF_name",
    "binding": "WF_name",
    "class_name": "WF_name"
  }]
}

Your scheduled(event, env, ctx) handler in worker.mjs would then kick off the Workflow instance (env.WF_name.create({...})). That's the documented pattern for triggering a Workflow on a schedule today.

That said, two things on the wrangler side that are real bugs even if your config wasn't intended to work:

1. The error Some triggers failed to deploy doesn't say what failed or why. The raw API response body would point straight at it (e.g. "unknown field schedules").
2. Unknown keys inside workflows[] entries pass validation silently. A validate_additional_workflow_props step that warns on unrecognized keys would have surfaced this at wrangler deploy time instead of letting the API kick it back.

Happy to put up a PR for either of those if the team thinks they're worth fixing.

[mike-git374]

The docs say "schedules" belongs in workflows[] in wrangler.json, see: https://developers.cloudflare.com/workflows/build/trigger-workflows/#schedule-a-workflow-directly
and
https://developers.cloudflare.com/changelog/post/2026-06-02-cron-workflows/

PR here: #13467

This is a new feature, you gave an example of the old way to do it, I can confirm old way is working, I can't get the new way to work yet.

[emily-shen]

Hi, your config looks like it should work - the workflow name definitely doesn't have to match the worker name 😅

What version of wrangler are you on? I have just tested this and it works on the latest version of wrangler for me, but possibly you are trying a version before this was added.

If you're on the latest version and its still not working, could you share your debug logs by running with the env vars WRANGLER_LOG=debug WRANGLER_LOG_SANITIZE=false.

[mike-git374]

It was wrangler version 4.100.0 and I tried again with new 4.101.0 and same issue.

In the debug logs you requested I see the error message: "workflows.api.error.workflow.cron_requires_paid_plan" so looks like it needs Workers paid plan. The docs should specify that this feature requires paid plan, see: https://developers.cloudflare.com/workflows/build/trigger-workflows/#schedule-a-workflow-directly

And the wrangler cli error should be more specific, it just says: "Some triggers failed to deploy"