# Cron triggers that actually fire

Cron Triggers execute on UTC time. Everything else people assume about them is where the failures live.

## The three requirements

1. A `scheduled` event handler in your Worker. Without the handler, the trigger fires into nothing.
2. The schedule in the Wrangler config under `triggers.crons`, as standard cron expressions:

```jsonc
{
  "triggers": {
    "crons": ["*/3 * * * *", "0 15 1 * *"]
  }
}
```

3. Deploy. Triggers defined only in config but never deployed do not exist.

## The three silent failures

- **Timezone**: schedules are UTC. `0 9 * * *` is 09:00 UTC, not your local 09:00. Convert explicitly.
- **No handler**: the Worker deploys fine, the dashboard shows the trigger, nothing happens because there is no `scheduled` listener.
- **`workers_dev = false` only**: a Worker with only a `scheduled` handler does not need `workers_dev` true; that is fine and expected, do not "fix" it by enabling.

## Environments

Cron triggers can differ per environment (`[env.dev.triggers]`). To remove all triggers in an environment, set `"crons": []` explicitly; an absent key inherits.

## Checklist

- After deploy, check the dashboard trigger list and invoke once manually if the schedule is sparse (a monthly cron is a long time to discover a misconfiguration).
- Log at the top of the `scheduled` handler: no logs plus no handler output is indistinguishable from "trigger never fired" without them.
- Free plan allows 5 cron triggers per account, Paid 250; count them if you run many Workers.