Mini RFC: Cron Triggers

[ObsidianMinor]

Cron triggers are out, but there isn't a way to configure them from wrangler. To support cron triggers, I propose we add a new triggers table with a crons field as an array of strings.

Example

name = "scheduled"
type = "javascript"
account_id = "..."

[triggers]
crons = ["* * * * *"]

name = "weekly"
type = "javascript"
account_id = "..."

[triggers]
crons = ["0 0 * JAN-JUN FRI", "0 0 * JUL-DEC SAT"]

[ObsidianMinor]

cc: @ashleymichal

[xtuc]

Since webpack doesn't allow emitting JavaScript modules syntax yet we should probably restrict to type javascript only

[ObsidianMinor]

Since webpack doesn't allow emitting JavaScript modules syntax yet we should probably restrict to type javascript only

We still support the original addEventListener form so this works without module support.

[simonhaenisch]

My scheduled worker doesn't need workers_dev but also doesn't need a route/routes because it only handles 'scheduled' events. I currently have to leave workers_dev = true, otherwise I'll get "Error: No deploy target specified" when trying to publish my worker.

Thus: triggers should be considered a deploy target as well 🤓

[ObsidianMinor]

Yeah, part of this work will be making multiple target deployments possible instead of exclusively zoned or zoneless.

[oliverpool]

Currently the dashboard indicates

If this Worker is managed by Wrangler, add Cron Triggers via CLI commands or to your wrangler.toml file instead.

However if I understand this issue correctly, this is not yet supported by wrangler.toml.

Do you have an estimate when this will be possible? (and maybe change the dashboard hint in the meantime...)

[ObsidianMinor]

@oliverpool I'm working full time on it, so it should be a PR sometime this week. You're also right that the dash is incorrect and I've submitted changes to remove that.