Skip detection is now live for Heroku Scheduler jobs.
View on the Heroku Elements Marketplace
You can add, edit, and delete Heroku Scheduler jobs, but not pause them, and maintenance mode doesn't stop them. Keep your jobs, check a config var at the top of each one, and switch them off and on with a single command.
Heroku Scheduler has no Run button, and heroku run skips the time to live a scheduled run gets. Start the job with heroku run:detached, then add the same TTL through the Platform API, so your test stops where a scheduled run would.
A Heroku Scheduler job that runs past its interval is stopped: Heroku sends the dyno SIGTERM, and on the Common Runtime it exits with status 143. Here is how to confirm that in your logs, and three ways to keep long work running to the end.
The Heroku CLI contains a lot of powerful CLI commands. Today we will dive into 2 of them: the heroku run and heroku run:detached commands. Both allow you to run a one-off process inside a Heroku one-off dyno right from the terminal, but how are they different and to what use cases does each apply?