Cloudflare has added Cron Triggers to Workers, letting developers run a Worker on a timed schedule rather than only in response to an incoming HTTP request. The feature is available today on the Workers free tier and on the paid tier, now called Workers Bundled.
How scheduled Workers run
A Cron Trigger sets a recurring, time-based invocation for a Worker, following the familiar Unix cron pattern for jobs that run at fixed intervals or at scheduled times. Unlike a traditional Worker, it does not fire on HTTP requests. Pulling the latest data from APIs and running integration tests on a preset schedule are two common applications.
"We're excited about Cron Triggers. Workers is crucial to our stack, so using this feature for live integration tests will boost the developer experience." - Brian Marks, Software Engineer at Bazaarvoice
Pricing and limits
Triggers carry no additional charge, and Cloudflare says scheduled Workers count toward the request cap on both tiers, with no hidden or extra fees. The company points out that competitors either charge extra for cron events or offer only a limited free tier, and it has chosen not to bill per trigger. Accounts have no cap on the number of triggers, but each Worker script may have at most 3. Plan limits are documented in the Workers documentation.
Why it can be free: routing to quiet machines
Edge nodes are named after the IATA airport code of the nearest city, and the network spans 200+ cities. HTTP Workers normally run near the request origin (SJC for the Bay Area, CDG for Paris) because latency matters when someone is waiting. For a scheduled job nobody is waiting on, a few milliseconds of extra latency carry far less weight, and that slack lets Cloudflare place the job wherever capacity is idle. A job scheduled from San Francisco at 7pm Pacific might run in Paris, where it is 4am and European traffic is low. Beyond this placement optimization, Cloudflare says Cron Trigger Workers behave like typical HTTP Workers and share the same performance and security properties.
Under the hood
Schedules created through the API become records in a database holding what is needed to execute the Worker on the given cron schedule. Another service continuously evaluates the state of the edge and distributes those schedules among cities. A service running in each node then polls for changes to its schedules and passes them to the runtime at the appropriate time. More implementation detail is available in the technical blog.
What comes after cron
Cloudflare frames Cron Triggers as a first step away from the idea that edge compute must be tied strictly to HTTP requests and responses. The roadmap calls for other trigger types, such as data or event-based triggers, with the aim of giving users more control over when their Workers run. The company also plans to keep refining its edge infrastructure selection, raising the possibility of triggers that let users run in the most energy-efficient data centers.
Cron Triggers are live now; they can be set up in the Workers dashboard by creating a new Worker and configuring a trigger.



