Why is cron running every minute?
I set a worker to run on an every-minute cron job (
* * * * * *
) just to test that the schedule was working, then I changed the cron job back to once-per-day (0 0 * * * *
). However, when I visit the log stream for the worker, I still see * * * * * *
triggering once per minute. The list of triggers for the worker explicitly show only one cron attached to the worker, 0 0
. Why is the per-minute * *
cron is still running, and how I can turn it off?
I am deploying via Wrangler, if that's relevant. My wrangler.toml
contains only one cron: 0 0
.
Attached are screenshots of the cron configuration.
I am worried that this will eat up all of my free compute. 😦

2 Replies
How recent ago did you change the cron config? It can take 20-30 minutes to settle after changing
Thank you. It was changed recently. I'll keep monitoring it to see if it stops.
I noticed that the code being executed changed immediately, so it was executing the once-per-day code, but it was still executing once-per-minute.