Cron Jobs 2.0
We heard you wanted a pony for your birthday, so we got you the next best thing: a new and improved scheduler. Trust us on this one.
We introduced the original scheduler some time ago to make it more convenient to run cron jobs reliably across a cluster and to avoid the problematic oh-but-the-machine-that-was-supposed-to run-the-cron-job-crashed situation.
So we did some tinkering. We ported the schedule to our new JavaScript engine, like the rest of Scalr (in fact it was the last piece that we needed to port over). This means that it’s faster and completely JavaScript- and JSON-driven, which opens the door for future API access. Furthermore, we rewrote the backend execution code to handle more edge cases.
So maybe you can’t braid its mane or paint its hooves, but you can start using it right away. If you had tasks running in the previous scheduler, they will continue to run in read-only view, and you’ll have the option of migrating them to the new one (the button says, not-so surprisingly, "Migrate all my tasks to new scheduler").
We want to avoid any issues with timezones and unexpected duplicate task runs, so we're not automatically migrating tasks set on the previous scheduler to the new one. We know when we shouldn’t horse around.
The new, awesom-er, scheduler
Tally-ho,
The Scalr “clock-is-ticking” team