CUNY Academic Commons

Ron Rennick

<p>When active, this plugin logs unsuccessful results of wp_remote_post calls from wp-cron to a sites’s options table with an option name of ra_http_WP_Http_Streams + timestamp. The option_value contains the results of the call.</p>
<p>This plugin is intended to be enabled only on sites that are experiencing cron issues as a troubleshooting aid. Once the cron issue had been identified and corrected, the plugin should be deactivated. When finished troubleshooting you should also remove the option records created by this plugin using your database management tool.</p>
<p>In a WP network use the <a href="https://wordpress.org/extend/plugins/plugin-premium-package-manager-for-wp-networks/" rel="ugc">Plugin Manager</a> to hide this plugin and prevent site admins from activating it.</p>
<p>This plugin was written by <a href="http://ronandandrea.com/" rel="nofollow ugc">Ron Rennick</a> in collaboration with the <a href="http://dev.commons.gc.cuny.edu/" rel="nofollow ugc">CUNY Academic Commons</a>.</p>


Cron Debug Log

Sayan Datta

<p>The WP-Cron system in WordPress is not a “real” cron system, which means events may not run exactly according to their schedule because the system relies on regular traffic to the website in order to trigger scheduled events.</p>
<h3>Reasons WP-Cron events can miss their schedule</h3>
<ul>
<li>Low traffic websites may not trigger the event runner often enough</li>
<li>A fatal error caused by a plugin or theme may break the event runner</li>
<li>A plugin or theme may intentionally or unintentionally break the event runner</li>
<li>BasicAuth, a firewall, or other access restrictions may block the event runner</li>
<li>A problem with your web hosting or web server may break the event runner</li>
<li>The <code>DISABLE_WP_CRON</code> configuration constant is set but no alternative cron runner has been put in place</li>
<li>Long-running events may temporarily block the event runner</li>
<li>High traffic websites may suffer from sequential processing issues that block the event runner</li>
</ul>
<p>The Advanced Cron Scheduler for WordPress plugin does alter the way that WordPress core runs cron events using the Action Scheduler Library.</p>
<p>Action Scheduler is a scalable, traceable job queue for background processing large sets of actions in WordPress. It’s specially designed to be distributed in WordPress plugins.</p>
<p>Action Scheduler works by triggering an action hook to run at some time in the future. Each hook can be scheduled with unique data, to allow callbacks to perform operations on that data. The hook can also be scheduled to run on one or more occassions.</p>
<p>Think of it like an extension to <code>do_action()</code> which adds the ability to delay and repeat a hook.</p>
<h3>Battle-Tested Background Processing</h3>
<p>Every month, Action Scheduler processes millions of payments for <a href="https://woocommerce.com/products/woocommerce-subscriptions/" rel="nofollow ugc">Subscriptions</a>, webhooks for <a href="https://wordpress.org/plugins/woocommerce/" rel="ugc">WooCommerce</a>, as well as emails and other events for a range of other plugins.</p>
<p>It’s been seen on live sites processing queues in excess of 50,000 jobs and doing resource intensive operations, like processing payments and creating orders, at a sustained rate of over 10,000 / hour without negatively impacting normal site operations.</p>
<p>This is all on infrastructure and WordPress sites outside the control of the plugin author.</p>
<p>If your plugin needs background processing, especially of large sets of tasks, Action Scheduler can help.</p>
<h3>Learn More</h3>
<p>To learn more about how to Action Scheduler works, and how to use it in your plugin, check out the docs on <a href="https://actionscheduler.org" rel="nofollow ugc">ActionScheduler.org</a>.</p>
<p>There you will find:</p>
<ul>
<li><a href="https://actionscheduler.org/usage/" rel="nofollow ugc">Usage guide</a>: instructions on installing and using Action Scheduler</li>
<li><a href="https://actionscheduler.org/wp-cli/" rel="nofollow ugc">WP CLI guide</a>: instructions on running Action Scheduler at scale via WP CLI</li>
<li><a href="https://actionscheduler.org/api/" rel="nofollow ugc">API Reference</a>: complete reference guide for all API functions</li>
<li><a href="https://actionscheduler.org/admin/" rel="nofollow ugc">Administration Guide</a>: guide to managing scheduled actions via the administration screen</li>
<li><a href="https://actionscheduler.org/perf/" rel="nofollow ugc">Guide to Background Processing at Scale</a>: instructions for running Action Scheduler at scale via the default WP Cron queue runner</li>
</ul>
<h3>Support</h3>
<ul>
<li>Community support via the <a href="https://wordpress.org/support/plugin/migrate-wp-cron-to-action-scheduler/" rel="ugc">support forums</a> at WordPress.org.</li>
</ul>
<h3>Contribute</h3>
<ul>
<li>Active development of this plugin is handled <a href="https://github.com/iamsayan/advanced-cron-scheduler/" rel="nofollow ugc">on GitHub</a>.</li>
<li>Feel free to <a href="https://github.com/iamsayan/advanced-cron-scheduler/" rel="nofollow ugc">fork the project on GitHub</a> and submit your contributions via pull request.</li>
</ul>
<h3>Credits</h3>
<p>Action Scheduler is developed and maintained by <a href="http://automattic.com/" rel="nofollow ugc">Automattic</a>.</p>


Advanced Cron Scheduler for WordPress

The Advanced Cron Scheduler for WordPress plugin helps to easily replace or migrate Native WordPress Cron to the Action Scheduler Library.

Cron Debug Log vs Advanced Cron Scheduler for WordPress