You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,13 @@ By default the plugin disables default WP cron processing. It is recommended to
25
25
26
26
## Frequently Asked Questions ##
27
27
28
+
### Deviations from WordPress Core ###
29
+
30
+
* Cron jobs are stored in a custom table and not in the `cron` option in wp_options. As long relevent code uses WP core functions for retrieving events and not direct SQL, all will stay compatible.
31
+
* Duplicate recurring events with the same action/args/schedule are prevented. If multiple of the same action is needed on the same schedule, can add an arbitrary number to the args array.
32
+
* When the cron control runner is running events, it does so via WP CLI. So the environment can be slightly different than that of a normal web request.
33
+
* The cron control runner can process multiple events in parallel, whereas core cron only did 1 at a time. By default, events with the same action will not run in parallel unless specifically granted permission to do so.
34
+
28
35
### Adding Internal Events ###
29
36
30
37
**This should be done sparingly as "Internal Events" bypass certain locks and limits built into the plugin.** Overuse will lead to unexpected resource usage, and likely resource exhaustion.
Copy file name to clipboardExpand all lines: readme.txt
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,13 @@ By default the plugin disables default WP cron processing. It is recommended to
25
25
26
26
== Frequently Asked Questions ==
27
27
28
+
= Deviations from WordPress Core =
29
+
30
+
* Cron jobs are stored in a custom table and not in the `cron` option in wp_options. As long relevent code uses WP core functions for retrieving events and not direct SQL, all will stay compatible.
31
+
* Duplicate recurring events with the same action/args/schedule are prevented. If multiple of the same action is needed on the same schedule, can add an arbitrary number to the args array.
32
+
* When the cron control runner is running events, it does so via WP CLI. So the environment can be slightly different than that of a normal web request.
33
+
* The cron control runner can process multiple events in parallel, whereas core cron only did 1 at a time. By default, events with the same action will not run in parallel unless specifically granted permission to do so.
34
+
28
35
= Adding Internal Events =
29
36
30
37
**This should be done sparingly as "Internal Events" bypass certain locks and limits built into the plugin.** Overuse will lead to unexpected resource usage, and likely resource exhaustion.
0 commit comments