Manage WP Crontrol with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• Logging is off until you turn it on, one hook at a time. Runs before that are not recorded, so the logs and insights start empty. Runs are kept for up to 30 days (at most the latest 10,000 runs on the site) and insights cover the last 7.
• A run marked completed can still have failed inside: in our test, a digest job completed while its email failed to send. The failure was only in the run's warning flag, failed-email count and log messages, not its errors.
• Run now is marked destructive by WP Crontrol, but WPVibe's approval page covers abilities that delete something or whose name says they run PHP, SQL or other code; run-event's name has no such word, so WPVibe runs it at once. It does the task's real work right away, emails and payments included, and for a WP Crontrol PHP cron event it runs that event's stored code, which is why the recipes ask first.
• An overdue event starts on the next visit to your site, and WPVibe's own requests count as visits, unless WP-Cron is switched off. Run now also clears WP-Cron's lock, so it can start while that run is still going: on our test site, Run now on an overdue task was followed by three overlapping runs of it in four seconds.
• Pausing applies to every event with that hook name. Runs that come due while paused are skipped, not run later, and a one-off event that comes due during the pause is used up. Only hooks that have scheduled events can be paused, and WP Crontrol's own PHP and URL cron events cannot. Pausing also stops the hook when a plugin fires it outside WP-Cron.
• The abilities can't create, edit or delete events, and never return a PHP event's code or a URL event's full address. The addresses of HTTP requests a run makes come back as the domain only, with the path and query redacted, but error text written by the task's own code is stored as it was written. Delete leftover events on the Cron Events screen.
• Running a PHP cron event through an ability also needs the edit_files capability, so it is refused where file editing is switched off (DISALLOW_FILE_EDIT or DISALLOW_FILE_MODS) or PHP cron events are disabled.
• Late means more than 10 minutes overdue. Many late events usually mean WP-Cron is not running at all, for example DISABLE_WP_CRON with no server cron job.
• An event with no action is not always left over: some active plugins attach their handler only while cron runs or when a setting is on. On our test site one such event belonged to LifterLMS, which was active. Check the plugin is gone before deleting its events.