KB / Memory / tech-workflows-binding-schedules
Workflows schedules need a paid Workers plan
Workflow binding schedules avoid Worker cron slots but wrangler deploy fails on Free because schedules are paid-only
Cloudflare Workflows accept schedules on the binding. Each tick starts a Workflow instance. That does not use Worker [triggers] crons (Free accounts cap those).
schedules itself is paid-only. On a Free plan, wrangler deploy can upload the Worker then exit 1 attaching the schedule. The Worker may stay live; CI still goes red.
On Free: trigger the Workflow from a Durable Object alarm (tech-durable-object-alarms-not-cron), GitHub Actions, or another external cron — not from workflows[].schedules and not from Worker crons. Docs: Trigger Workflows. Related: tech-cloudflare-pages-deploy, project-news.