Dragon Cron Manager

Run leaves your existing booking in place when WordPress refuses the reschedule, and trash and log actions no longer report a failed save as a success.

What's fixed in 1.0.10

• "Run" no longer drops a recurring event. When you ran an event and WordPress refused the new booking (for example a plugin blocking scheduling), the event was removed from the schedule while the message still said "rescheduled". The existing booking is now left untouched until the replacement is confirmed in the schedule, and the reason for a refusal is shown.
• Trashing an event is safe against a failed save. The event is only unscheduled once its trash copy is confirmed saved, so a failed write can no longer remove an event that has no trash copy to restore.
• Trash actions report what really happened. Restore, permanent delete and Empty trash now check that the change was saved and tell you when it was not, instead of claiming success. Restoring an event that is already scheduled is refused instead of booking it twice.
• "Clear logs" reports a database refusal instead of saying the logs were cleared.
• Restoring a one-off event from the trash works again. A trashed single event could not be restored whenever any other event shared its hook and arguments, even at a completely different time, and the screen then suggested permanently deleting it. WordPress allows several one-off events with the same hook at different times, so only a genuine second recurring booking is refused now.

No settings, data or behaviour changes otherwise.

The run log now records scheduled cron events as they actually run — not just manual runs — and you can schedule a brand-new event straight from the dashboard.

= 1.0.9 =

• New: automatic WP-Cron runs are now logged as they happen, with duration and success/failure, so the Run Log and the Cron Doctor reflect what really runs on schedule instead of only manual "Run Now" tests. A new Source column marks each entry as Automatic or Manual.
• New: "Add Event" — schedule a new single or recurring cron event, with arguments, right from the dashboard.

Security & reliability update: "Run Now" now only executes cron events that are genuinely scheduled, and events whose arguments contain special characters run reliably again.

= 1.0.8 =

• Security: "Run Now" and "Test" now only fire events that actually exist in the WP-Cron schedule, matched by hook and arguments. A hook merely having a listener is no longer enough to trigger it — this prevents unintended execution of other code paths, especially on multisite.
• Fixed: cron event arguments containing tag-like or whitespace characters are no longer altered before matching, so those events run and reschedule correctly.

Tested and verified on WordPress 7.1.

• Compatibility: tested up to WordPress 7.1.

Performance: removes a small database cost that ran on every page load, and stops trashed-cron data loading on every request. The log tab is now honestly labelled Run Log.

Your data now survives uninstall by default.

Uninstalling no longer deletes the plugin's data unless you explicitly opt in first, so removing it to debug — or coming back later — keeps everything intact. Where the plugin has a settings screen you'll find a new "Delete all data on uninstall" option; leave it off to keep your data.

A cleaner, consistent look: the Dragon design system arrives.

This release brings Dragon Core's design system to every screen: a consistent header with the Dragon mark, cleaner tables, and unified status colours across the whole plugin family. Purely visual — everything behaves exactly as before.

New Diagnose button: when your cron is stuck, one click tells you exactly why.

The health bar now has a Diagnose button that runs a live root-cause check instead of just listing overdue tasks. It detects a missing system cron (and gives you the exact crontab line to add), a site that cannot reach its own cron endpoint (with the exact error — basic auth, firewall, or DNS), a crashed run still holding the cron lock, and starved queues on quiet sites. Running a diagnosis also kicks the queue, so overdue tasks catch up immediately.

• Initial release
• View and run cron events
• Execution logging
• Health diagnostics