DE

↑ ↓ select, Enter open, Esc close

List scheduled WP-Cron events

harmlessWP-CLIalle
Adjust the values, the command updates live
user@server
wp cron event list --fields=hook,next_run_relative,recurrence --path=/var/www/vhosts/example.com/httpdocs

Lists all registered WP-Cron events with hook name, time until the next run and recurrence interval. If many events show “now” or a time in the past, WP-Cron is not running reliably. Orphaned events from uninstalled plugins also stand out here.

Also searched as

  • check wordpress cron
  • scheduled posts not publishing
  • list wordpress cron jobs

Related one-liners

All in WP-CLI

Deactivate a single plugin despite a PHP fatal error

$wp plugin deactivate woocommerce --skip-plugins --skip-themes --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Deactivate all plugins and save the active list

$wp plugin list --status=active --field=name --path=/var/www/vhosts/example.com/httpdocs > /var/www/vhosts/example.com/active-plugins.txt && wp plugin deactivate --all --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Delete a scheduled WP-Cron event

$wp cron event delete old_plugin_daily_event --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Enable the WordPress debug log without displaying errors

$wp config set WP_DEBUG true --raw --path=/var/www/vhosts/example.com/httpdocs && wp config set WP_DEBUG_LOG true --raw --path=/var/www/vhosts/example.com/httpdocs && wp config set WP_DEBUG_DISPLAY false --raw --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Run due WP-Cron events immediately

$wp cron event run --due-now --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Switch to a default WordPress theme

$wp theme activate twentytwentyfour --skip-themes --skip-plugins --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.