## TL;DR

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.

## Steps

1. - **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.

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

## When to use

You are seeing this: Cron Triggers execute on UTC time. Use this skill when you run into "Workers cron triggers: schedules that actually fire".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
