Title: WP Crontrol
Author: John Blackbourn
Published: <strong>6. Januar 2008</strong>
Last modified: 28. Januar 2026

---

Plugins durchsuchen

![](https://ps.w.org/wp-crontrol/assets/banner-772x250.jpg?rev=3528147)

![](https://ps.w.org/wp-crontrol/assets/icon.svg?rev=3528147)

# WP Crontrol

 Von [John Blackbourn](https://profiles.wordpress.org/johnbillion/)

[Herunterladen](https://downloads.wordpress.org/plugin/wp-crontrol.1.21.0.zip)

 * [Details](https://de.wordpress.org/plugins/wp-crontrol/#description)
 * [Rezensionen](https://de.wordpress.org/plugins/wp-crontrol/#reviews)
 * [Entwicklung](https://de.wordpress.org/plugins/wp-crontrol/#developers)

 [Support](https://wordpress.org/support/plugin/wp-crontrol/)

## Beschreibung

WP Crontrol enables you to take control of the scheduled cron events on your WordPress
website or WooCommerce store. From the admin screens you can:

 * View all scheduled cron events along with their arguments, schedule, callback
   functions, and when they are next due.
 * Edit, delete, pause, resume, and immediately run cron events.
 * Neue Cron-Ereignisse hinzufügen.
 * Cron-Ereignisse per Massenverarbeitung löschen.
 * Füge individuelle Cron-Zeitpläne hinzu und entferne sie.
 * Export and download cron event lists as a CSV file.

WP Crontrol is aware of timezones, will alert you to events that have no actions
or that have missed their schedule, and will show you a helpful warning message 
if it detects any problems with your cron system.

### Nutzung

 1. Gehe zum Menü `Werkzeuge  Cron-Ereignisse`, um Cron-Ereignisse zu verwalten.
 2. Gehe zum Menü `Einstellungen  Cron-Zeitpläne`, um Cron-Zeitpläne zu verwalten.

### Dokumentation

[Extensive documentation on how to use WP Crontrol and how to get help for error messages that it shows is available on the WP Crontrol website](https://wp-crontrol.com/docs/how-to-use/).

### Für Websitebetreiber

Owners of WordPress websites and WooCommerce stores use WP Crontrol to ensure that
scheduled cron events run correctly and efficiently. By providing complete control
over cron events, WP Crontrol helps you:

 * **Improve reliability**: Address missed or failed cron events, ensuring your 
   website or WooCommerce store continues to function as expected.
 * **Enhance security**: Monitor and control cron events to ensure automatic update
   checks are performed as they should.
 * **Simplify management**: Add, edit, delete, and pause cron events from a user-
   friendly interface, without needing to write any code.
 * **Gain insights**: Export cron event data for analysis or reporting.
 * **Action Scheduler compatibility**: Full support for the Action Scheduler system
   in WooCommerce, which is used to process recurring payments, subscriptions, and
   background orders.
 * **Clarity of times and timezones**: All times are shown with a clear and accurate
   indication of which timezone applies. No more guesswork!

### Für Entwickler

Developers use WP Crontrol to streamline and debug their WordPress development process:

 * **Enhanced debugging**: Identify and troubleshoot issues with scheduled tasks,
   ensuring your scheduled events and their callbacks run as expected.
 * **Custom schedules**: Create and manage custom cron schedules to fit the specific
   needs of your website, plugins, or themes, providing greater flexibility than
   just the core schedules.
 * **Efficient workflow**: Add, edit, and delete cron events directly from the WordPress
   admin interface, saving time and reducing the need for manual coding.
 * **Insightful monitoring**: Get insight into the performance and behavior of your
   scheduled tasks, allowing for optimization and better resource management.
 * **Accurate debugging**: WP Crontrol goes to great lengths to ensure that running
   an event manually does so in a manner which exactly matches how WordPress core
   runs schdeuled events. This ensures that you can debug events accurately and 
   with confidence.

### Andere Plugins

I maintain several other plugins for developers. Check them out:

 * [Query Monitor](https://wordpress.org/plugins/query-monitor/) is the developer
   tools panel for WordPress.
 * [User Switching](https://wordpress.org/plugins/user-switching/) provides instant
   switching between user accounts in WordPress.

### Privacy Statement

WP Crontrol is private by default and always will be. It does not send data to any
third party, nor does it include any third party resources. [WP Crontrol’s full privacy statement can be found here](https://wp-crontrol.com/privacy/).

### Accessibility Statement

WP Crontrol aims to be fully accessible to all of its users. [WP Crontrol’s full accessibility statement can be found here](https://wp-crontrol.com/accessibility/).

## Screenshots

 * [[
 * Cron events can be modified, deleted, and executed
 * [[
 * New cron events can be added
 * [[
 * New cron schedules can be added, giving plugin developers more options when scheduling
   events

## FAQ

### Funktioniert dieses Plugin mit PHP 8?

Yes, it’s actively tested and working up to PHP 8.4.

### I get the error „There was a problem spawning a call to the WP-Cron system on your site“. How do I fix this?

[You can read all about problems spawning WP-Cron on the WP Crontrol website](https://wp-crontrol.com/help/problems-spawning-wp-cron/).

### Why do some cron events miss their schedule?

[You can read all about cron events that miss their schedule on the WP Crontrol website](https://wp-crontrol.com/help/missed-cron-events/).

### Why do some cron events reappear shortly after I delete them?

If the event is added by a plugin then the plugin most likely rescheduled the event
as soon as it saw that the event was missing. To get around this you can instead
use the „Pause this hook“ action which means it’ll remain in place but won’t perform
any action when it runs.

### Is it safe to delete cron events?

This depends entirely on the event. You can use your favourite search engine to 
search for the event name in order to find out which plugin it belongs to, and then
decide whether or not to delete it.

If the event shows „None“ as its action then it’s usually safe to delete. Please
see the other FAQs for more information about events with no action.

### Why can’t I delete some cron events?

The WordPress core software uses cron events for some of its functionality and removing
these events is not possible because WordPress would immediately reschedule them
if you did delete them. For this reason, WP Crontrol doesn’t let you delete these
persistent events from WordPress core in the first place.

If you don’t want these events to run, you can use the „Pause this hook“ action 
instead.

### What happens when I pause an event?

Pausing an event will disable all actions attached to the event’s hook. The event
itself will remain in place and will run according to its schedule, but all actions
attached to its hook will be disabled. This renders the event inoperative but keeps
it scheduled so as to remain fully compatible with events which would otherwise 
get automatically rescheduled when they’re missing.

As pausing an event actually pauses its hook, all events that use the same hook 
will be paused or resumed when pausing and resuming an event. This is much more 
useful and reliable than pausing individual events separately.

### What happens when I resume an event?

Resuming an event re-enables all actions attached to the event’s hook. All events
that use the same hook will be resumed.

### What does it mean when „None“ is shown for the Action of a cron event?

This means the cron event is scheduled to run at the specified time but there is
no corresponding functionality that will be triggered when the event runs, therefore
the event is useless.

[You can read all about events with no action on the WP Crontrol website](https://wp-crontrol.com/help/no-action-cron-events/).

### How do I change the next run time or the schedule of a cron event?

You can change the time and schedule of a cron event by clicking the „Edit“ link
next to the event.

### Warum werden Änderungen, die ich an Cron-Events mache, nicht gespeichert?

[You can read all about problems with editing cron events on the WP Crontrol website](https://wp-crontrol.com/help/problems-managing-events/).

### Can I export a list of cron events?

Yes, a CSV file of the event list can be exported and downloaded via the „Export“
button on the cron event listing screen. This file can be opened in any spreadsheet
application.

### Kann ich ein historisches Protokoll aller Cron-Events sehen, die auf meiner Website gelaufen sind?

Not yet, but I hope to add this functionality soon.

### Can I see a historical log of edits, additions, and deletions of cron events and schedules?

Yes. The excellent [Simple History plugin](https://wordpress.org/plugins/simple-history/)
has built-in support for logging actions performed via WP Crontrol.

### Was ist der Sinn hinter dem Hinzufügen von neuen Cron-Zeitplänen?

Cron-Zeitplöne werden von WordPress und Plugins benutzt, um Ereignisse zu planen,
die in normalen Intervallen ausgeführt werden. Intervalle müssen vom WordPress-Core
oder von einem Plugin bereitgestellt werden, um benutzt werden zu können. Als Beispiel
bieten viele Sicherungs-Plugins Unterstützung für periodische Sicherungen an. Um
eine wöchentliche Sicherung zu erstellen, muss ein wöchentlicher Zeitplan zuerst
in WP Crontrol hinzugefügt werden, damit ein Sicherungs-Plugin diesen Zeitplan als
Intervall benutzen kann.

### Wie erstelle ich ein neues Cron-Ereignis?

Es sind zwei Schritte erforderlich, um ein funktionierendes Cron-Ereignis zu erhalten,
das regelmäßig ausgeführt wird. Der erste Schritt besteht darin, WordPress den Hook
mitzuteilen. Das ist der Teil, für den WP Crontrol erstellt wurde. Der zweite Schritt
ist, eine Funktion auszuführen, wenn dein Hook ausgeführt wird.

_Step One: Adding the event_

From the Tools  Cron Events menu, click on Add Cron Event. Fill out the details 
of the event. You’re best off using a hook name that conforms to normal PHP variable
naming conventions. The schedule is how often the event will be executed. If you
don’t see a good interval, then add one in the Settings  Cron Schedules menu.

_Schritt Zwei: Schreiben der Funktion_

Dieser Teil muss in den PHP-Code (beispielsweise in der `functions.php` deines Themes).
Um deinen Hook auszuführen, führt WordPress eine Action aus. Aus diesem Grund müssen
wir WordPress sagen, welche Funktion ausgeführt werden soll, wenn diese Action läuft.
Die folgende Zeile erledigt das:

    ```
    add_action( 'my_hookname', 'my_function' );
    ```

Der nächste Schritt ist das Schreiben deiner Funktion. Hier gibt es ein einfaches
Beispiel:

    ```
    function my_function() {
        wp_mail( 'hello@example.com', 'WP Crontrol', 'WP Crontrol rocks!' );
    }
    ```

### Wie kann ich ein Cron-Event erstellen, welches eine URL ansteuert?

From the Tools  Cron Events menu, click on Add Cron Event. Select the „URL cron 
event“ option, fill out the details, and press the „Add Event“ button.

[You can read all about the features and security of URL cron events on the WP Crontrol website](https://wp-crontrol.com/docs/url-cron-events/).

### Wie erstelle ich ein neues PHP-Cron-Ereignis?

From the Tools  Cron Events menu, click on Add Cron Event. Select the „PHP cron 
event“ option and enter the schedule and next run time. The event schedule is how
often your event will be executed. If you don’t see a good interval, then add one
in the Settings  Cron Schedules menu. In the „PHP Code“ area, enter the PHP code
that should be run when your cron event is executed. You don’t need to provide the
PHP opening tag (`<?php`).

Creating, editing, and running PHP cron events is subject to restrictive security
permissions. [You can read all about the features and security of PHP cron events on the WP Crontrol website](https://wp-crontrol.com/docs/php-cron-events/).

### Welche Benutzer können Cron-Ereignisse und -Zeitpläne verwalten?

Nur Benutzer mit der `manage_options`-Berechtigung können Cron-Ereignisse und -Zeitpläne
verwalten. Standardmäßig haben nur Administratoren diese Berechtigung.

### Welche Benutzer können PHP-Cron-Ereignisse verwalten? Ist das gefährlich?

Nur Benutzer mit der Berechtigung `edit_files` können PHP-Cron-Ereignisse verwalten.
Das heißt, wenn ein Benutzer keine Dateien im WordPress-Adminbereich bearbeiten 
darf (d. h. durch den Plugin- oder Theme-Editor), kann er auch keine PHP-Cron-Ereignisse
in WP Crontrol hinzufügen, bearbeiten oder löschen. Standardmäßig haben nur Administratoren
diese Berechtigung und bei aktiver Multisite haben nur Super-Administratoren diese
Berechtigung.

Wenn die Dateibearbeitung über die Konfigurations-Konstanten `DISALLOW_FILE_MODS`
oder `DISALLOW_FILE_EDIT` deaktiviert wurden, hat kein Benutzer die Berechtigung`
edit_files`, wodurch das Hinzufügen, Bearbeiten oder Löschen eines PHP-Cron-Ereignisses
nicht erlaubt ist.

Deshalb ändert sich die erforderliche Berechtigung mit aktiviertem WP Crontrol nicht,
um beliebigen PHP-Code auszuführen.

If the `CRONTROL_DISALLOW_PHP_EVENTS` constant is defined and set to `true`, then
PHP cron events will be disabled completely. Any existing PHP cron events will remain
in place (and can be deleted if user permissions allow) but their PHP code will 
not be executed when the event runs, and no PHP cron events can be added, edited,
or run.

[You can read all about the features and security of PHP cron events on the WP Crontrol website](https://wp-crontrol.com/docs/php-cron-events/).

### Sind irgendwelche WP-CLI-Befehle verfügbar?

The cron commands which were previously included in WP Crontrol are now part of 
WP-CLI itself. See `wp help cron` for more info.

### What happens when I deactivate the WP Crontrol plugin?

[You can read all about what happens when you deactivate the plugin on the WP Crontrol website](https://wp-crontrol.com/docs/deactivation/).

### Wie kann ich ein Sicherheitslücke melden?

[You can report security bugs through the official WP Crontrol Vulnerability Disclosure Program on Patchstack](https://patchstack.com/database/vdp/wp-crontrol).
The Patchstack team helps validate, triage, and handle any security vulnerabilities.

### Who took the photo in the plugin header image?

The photo was taken by [Michael Pardo](https://www.flickr.com/photos/michaelpardo/21453119315)
and is in the public domain.

## Rezensionen

![](https://secure.gravatar.com/avatar/e2987b2396b9c5cd5b6d4ae5ead033949fe1876bc53b71c8f887abc393e2544c?
s=60&d=retro&r=g)

### 󠀁[Hmm. Nothing actually deletes](https://wordpress.org/support/topic/hmm-nothing-actually-deletes/)󠁿

 [patboran](https://profiles.wordpress.org/patboran/) 10. Februar 2026 4 Antworten

Not currently working for me, but developer points out that the issue is probably
at my site rather than with the app. Which I will, of course, look into.

![](https://secure.gravatar.com/avatar/5259aad43e4f23bf29d16ec6968167079e141954c31c62b6f95e5643b9b7d584?
s=60&d=retro&r=g)

### 󠀁[Must-Use Plugin](https://wordpress.org/support/topic/must-use-plugin-35/)󠁿

 [eLmore](https://profiles.wordpress.org/elmore/) 8. Februar 2026

Always use this plugin to debug my cron jobs. It’s extremely simple and easy to 
use.

![](https://secure.gravatar.com/avatar/ea6d0543003811bf39dfef74a31f15287a49823fc40fb5011edcc3c0d71614b7?
s=60&d=retro&r=g)

### 󠀁[Works](https://wordpress.org/support/topic/works-2268/)󠁿

 [kloddant](https://profiles.wordpress.org/kloddant/) 22. Januar 2026

Does what it is supposed to.

![](https://secure.gravatar.com/avatar/abe2555d2ad23e504c80b6acefb560b411cecf7ba672675a21d9e66cc429196e?
s=60&d=retro&r=g)

### 󠀁[Life saver](https://wordpress.org/support/topic/life-saver-483/)󠁿

 [orangeracoon](https://profiles.wordpress.org/orangeracoon/) 4. Dezember 2025

during last summer, I was having an almost impossible problem of my tables that 
would Stop rendering after around 24 hours, initially I thought it was a Cloudflare
issue , so I spent weeks excluding rules from caching. It was not until I installed
WPCron did it learn that Elementor was running one particular Cron job that were
completely unrelated to any of the material or topic which was breaking the rendering
of the tables . I literally worked on addressing this bug on and off for several
months . it was eye opening to see the number of Cron jobs that WordPress plugins
run . And for a a free plugin , I think it is a must have tool to have , I would
even consider making it part of core. Thank You . 😊

![](https://secure.gravatar.com/avatar/d112eff18652604126b88495a8cfc3f66b2a56489833597f47743b5dc11fa08a?
s=60&d=retro&r=g)

### 󠀁[A way to see, create, remove and pause WordPress Cron Jobs.](https://wordpress.org/support/topic/a-way-to-see-create-remove-and-pause-wordpress-cron-jobs/)󠁿

 [Farzad](https://profiles.wordpress.org/farzadjozaghi/) 20. August 2025

I Mainly use it to watch how my Cron Jobs are working.

![](https://secure.gravatar.com/avatar/9bf7181dbe7d9cfa5be8ca505e771ba5135e9e33b8175961fb43d54ee8043809?
s=60&d=retro&r=g)

### 󠀁[Very convenient](https://wordpress.org/support/topic/very-convenient-96/)󠁿

 [Anonymous User](https://profiles.wordpress.org/anonymized-23336172/) 18. August
2025

I can do all these things on my site’s backend without having to mess with databases.

 [ Alle 163 Rezensionen lesen ](https://wordpress.org/support/plugin/wp-crontrol/reviews/)

## Mitwirkende und Entwickler

„WP Crontrol“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin
mitgewirkt:

Mitwirkende

 *   [ John Blackbourn ](https://profiles.wordpress.org/johnbillion/)
 *   [ scompt ](https://profiles.wordpress.org/scompt/)

„WP Crontrol“ wurde in 24 Sprachen übersetzt. Danke an [die Übersetzer](https://translate.wordpress.org/projects/wp-plugins/wp-crontrol/contributors)
für ihre Mitwirkung.

[Übersetze „WP Crontrol“ in deine Sprache.](https://translate.wordpress.org/projects/wp-plugins/wp-crontrol)

### Interessiert an der Entwicklung?

[Durchstöbere den Code](https://plugins.trac.wordpress.org/browser/wp-crontrol/),
sieh dir das [SVN-Repository](https://plugins.svn.wordpress.org/wp-crontrol/) an
oder abonniere das [Entwicklungsprotokoll](https://plugins.trac.wordpress.org/log/wp-crontrol/)
per [RSS](https://plugins.trac.wordpress.org/log/wp-crontrol/?limit=100&mode=stop_on_copy&format=rss).

## Änderungsprotokoll

### 1.21.0 (28 January 2026)

 * Adds support for invalid args in cron events by relaxing the strict typing and
   showing a warning on the listing and editing screens.

### 1.20.0 (17 December 2025)

 * Confirms support for WordPress 6.9
 * Minor UI and UX improvements
 * Some architectural changes to prepare for future enhancements

### 1.19.3 (23 October 2025)

 * Corrects the handling of closures as cron event actions.

### 1.19.2 (19 August 2025)

 * Security: Hardens the „URL cron event“ functionality by rejecting disallowed 
   URLs. [More information see the security advisory](https://github.com/johnbillion/wp-crontrol/security/advisories/GHSA-35c5-67fm-cpcp).
 * Tweaks the display of some non-persistent WordPress core hooks when Multisite
   is enabled.

### 1.19.1 (3 June 2025)

 * Reinstates the ability to edit the Action Scheduler event.

### 1.19.0 (23 April 2025)

 * Confirms support for WordPress 6.8
 * Further improvements to the display of dates, intervals, and timezones for increased
   clarity
 * Adds more contextual help links for problematic events
 * Various UI and UX improvements

### 1.18.0 (13 January 2025)

 * Introduces support for a `CRONTROL_DISALLOW_PHP_EVENTS` constant to fully disable
   the PHP cron event functionality. [Full documentation here](https://wp-crontrol.com/docs/php-cron-events/).
 * Further improvements to how time durations and timezone information is displayed.

### 1.17.1 (22 November 2024)

 * Confirms support for WordPress 6.7
 * Avoids some warnings when running on PHP 8.3 and 8.4

### 1.17.0 (15 July 2024)

 * Introduces [a new cron event type for sending a request to a URL](https://wp-crontrol.com/docs/url-cron-events/)
 * Confirms support for WordPress 6.6
 * Improves various aspects of the cron management interface and language

### 1.16.3 (19 April 2024)

 * Corrects the displayed PHP cron event name if one is provided

### Earlier versions

For the changelog of earlier versions, [refer to the releases page on GitHub](https://github.com/johnbillion/wp-crontrol/releases).

## Meta

 *  Version **1.21.0**
 *  Zuletzt aktualisiert **vor 4 Monaten**
 *  Aktive Installationen **300.000+**
 *  WordPress-Version ** 6.4 oder höher **
 *  Getestet bis **6.9.4**
 *  PHP-Version ** 7.4 oder höher **
 *  Sprachen
 * [Chinese (Taiwan)](https://tw.wordpress.org/plugins/wp-crontrol/), [Czech](https://cs.wordpress.org/plugins/wp-crontrol/),
   [Dutch](https://nl.wordpress.org/plugins/wp-crontrol/), [Dutch (Belgium)](https://nl-be.wordpress.org/plugins/wp-crontrol/),
   [English (Australia)](https://en-au.wordpress.org/plugins/wp-crontrol/), [English (Canada)](https://en-ca.wordpress.org/plugins/wp-crontrol/),
   [English (New Zealand)](https://en-nz.wordpress.org/plugins/wp-crontrol/), [English (UK)](https://en-gb.wordpress.org/plugins/wp-crontrol/),
   [English (US)](https://wordpress.org/plugins/wp-crontrol/), [French (France)](https://fr.wordpress.org/plugins/wp-crontrol/),
   [German](https://de.wordpress.org/plugins/wp-crontrol/), [Italian](https://it.wordpress.org/plugins/wp-crontrol/),
   [Japanese](https://ja.wordpress.org/plugins/wp-crontrol/), [Korean](https://ko.wordpress.org/plugins/wp-crontrol/),
   [Persian](https://fa.wordpress.org/plugins/wp-crontrol/), [Polish](https://pl.wordpress.org/plugins/wp-crontrol/),
   [Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-crontrol/), [Russian](https://ru.wordpress.org/plugins/wp-crontrol/),
   [Spanish (Chile)](https://cl.wordpress.org/plugins/wp-crontrol/), [Spanish (Colombia)](https://es-co.wordpress.org/plugins/wp-crontrol/),
   [Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/wp-crontrol/), [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/wp-crontrol/),
   [Spanish (Spain)](https://es.wordpress.org/plugins/wp-crontrol/), [Spanish (Venezuela)](https://ve.wordpress.org/plugins/wp-crontrol/)
   und [Swedish](https://sv.wordpress.org/plugins/wp-crontrol/).
 *  [Übersetze in deine Sprache](https://translate.wordpress.org/projects/wp-plugins/wp-crontrol)
 * Schlagwörter
 * [cron](https://de.wordpress.org/plugins/tags/cron/)[crontrol](https://de.wordpress.org/plugins/tags/crontrol/)
   [debug](https://de.wordpress.org/plugins/tags/debug/)[woocommerce](https://de.wordpress.org/plugins/tags/woocommerce/)
   [wp cron](https://de.wordpress.org/plugins/tags/wp-cron/)
 *  [Erweiterte Ansicht](https://de.wordpress.org/plugins/wp-crontrol/advanced/)

## Bewertungen

 4.5 von 5 Sternen.

 *  [  139 5-Sterne-Rezensionen     ](https://wordpress.org/support/plugin/wp-crontrol/reviews/?filter=5)
 *  [  2 4-Sterne-Rezensionen     ](https://wordpress.org/support/plugin/wp-crontrol/reviews/?filter=4)
 *  [  1 3-Sterne-Rezension     ](https://wordpress.org/support/plugin/wp-crontrol/reviews/?filter=3)
 *  [  0 2-Sterne-Rezensionen     ](https://wordpress.org/support/plugin/wp-crontrol/reviews/?filter=2)
 *  [  21 1-Sterne-Rezensionen     ](https://wordpress.org/support/plugin/wp-crontrol/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/wp-crontrol/reviews/#new-post)

[Alle Rezensionen anzeigen](https://wordpress.org/support/plugin/wp-crontrol/reviews/)

## Mitwirkende

 *   [ John Blackbourn ](https://profiles.wordpress.org/johnbillion/)
 *   [ scompt ](https://profiles.wordpress.org/scompt/)

## Support

Behobene Probleme in den letzten zwei Monaten:

     4 von 4

 [Support-Forum anzeigen](https://wordpress.org/support/plugin/wp-crontrol/)

## Spenden

Möchtest du die Weiterentwicklung dieses Plugins unterstützen?

 [ Für dieses Plugin spenden ](https://github.com/sponsors/johnbillion)