Automation & Developer
Cron Manager & Scheduler
Every scheduled task on one screen: when it last ran and what it said, a log of every run, retries after a failure, your own interval or a pause for any task, Run now, and an alert when a task fails or falls behind, on a clock that does not wait for visitors.
Description
Every scheduled task on one screen: when it last ran and what it said, a log of every run, retries after a failure, your own interval or a pause for any task, Run now, and an alert when a task fails or falls behind, on a clock that does not wait for visitors.
What it does
- A clock that does not wait for visitors: on Cloudflare a Cron Trigger every five minutes, on Node a timer in the site's own server every minute (from Core 0.1.58); a system scheduler or uptime monitor opening /_whd/cron also works
- Every scheduled task on one screen: the module it belongs to, how often it runs, when it last ran, what it said, when it is next due, and whether it is on time, running, paused, failing or overdue
- A log of every run, whatever started it (the clock, a visit, a ping, Run now), with how long it took and what it said, kept for the days you choose (at most 5,000 runs)
- Run now for any task, and a plain line in the log when a run is refused because the task is already running
- Retries after a failure, sooner than the next normal run, each waiting twice as long as the one before, never later than the normal run
- Your own interval for any task, in plain words (every 5 minutes to once a week), or back to the module's own
- Pause any task, and start it again
- Overdue tasks found and logged, and a stopped clock noticed
- Administrators told on the dashboard, and by email at most once a day for each task, after the failures in a row you choose and when a task is overdue
- One run at a time: Core claims each task before running it, so the clock, a visit, a ping and Run now never run it together
- Not yet: Changing how often the clock itself fires: on Cloudflare it is the Cron Trigger in the site's wrangler.jsonc, changed there and published again; on Node it is fixed at every minute. No task runs more often than every five minutes. Not built yet.
- Not yet: Sites published before Core 0.1.58 on Cloudflare have no Cron Trigger until their wrangler.jsonc gains the two lines (`main` and `triggers`) and the site is published again; until then tasks run after visits and pings, as before. Not built yet.
- Not yet: New jobs written by the owner (code, or a web address to call on a schedule): only tasks that modules register can run. A job that runs code from a settings screen, or calls an address an owner types, is not offered. Not built yet.
- Not yet: External ping integration (a hosted pinging service): any service that opens /_whd/cron works, but none is set up from here. Not built yet.
- Not yet: A run that takes longer than ten minutes can be started a second time: Core lets a claim go after ten minutes. On Cloudflare a run cannot last that long. Not built yet.
Stands in for
WP Crontrol.
These are other companies' products, named only to say what job this module does. Hostless Duck is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From WP Crontrol
- Comes across: Nothing is carried. It reads WordPress's list of scheduled jobs and reports each one: WordPress's own housekeeping (Core does its own), scheduled publishing (Core needs no job), jobs of plugins that have a module here (the module runs its own task), and other plugins' jobs, which nothing runs here.
- Does not: The jobs themselves (they call WordPress code), WP Crontrol's PHP jobs (never copied or run), its URL jobs (this site never calls an address an import names), its custom schedules, and the time each job was next due.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Advanced Cron Manager
- Comes across: Nothing is carried. It reads WordPress's list of scheduled jobs, which Advanced Cron Manager shows and edits, and reports what does each job's work on this site.
- Does not: The jobs themselves, and Advanced Cron Manager's pauses, logs and custom schedules, which it keeps in its own tables, not in WordPress's list.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
- 1.0.0November 21, 2026
Cron Manager & Scheduler 1.0.0: every scheduled task on one screen, Core's and every module's, with when it last ran and what it said; a log of every run and what started it; Run now; retries after a failure, each waiting twice as long; your own interval in plain words, or a pause; overdue tasks and a stopped clock found; administrators told on the dashboard and by email, at most once a day for each task. Reports what WP Crontrol and Advanced Cron Manager jobs become here; carries none.
Get Cron Manager & Scheduler when Hostless Duck opens
Hold a place for your site. One form on the home page: your WordPress address, then your email.
