TillFoundry Scheduler Watchdog

Changelog

0.1.7

• Fixed: the Flag a hook as slow above this average duration setting now actually decides which hooks are reported as slow. Raising the threshold hides faster hooks from the slowest-hooks table and the REST response, and lowering it surfaces more; previously the value was saved and shown but never applied, so the setting was a no-op and the on-screen promise was false.
• Fixed: every numeric setting now enforces its declared minimum on save. A crafted or malformed request could previously store 0 for fields documented as 1 or more — the top-hooks limit, the slow-hook threshold, the failure and stall thresholds, the queue-depth warning, the cleanup batch size and the retention ages — even though the on-screen field showed a floor. The 60-second minimum for the sample interval and the 7-day/30-day cleanup floors are unchanged.
• Fixed: the Action Scheduler is required admin notice now appears on the plugin’s own screens instead of only the WordPress dashboard. The dismissal check matched the text domain rather than the real screen id, so the notice was confined to index.php and a merchant whose Action Scheduler was missing never saw it where they could act on it.
• Fixed: the admin stylesheet and script are now enqueued using the plugin’s declared menu slug, matching the same real screen ids, so the admin bundle loads on every Scheduler Watchdog screen and on no unrelated admin page.

0.1.6

• Changed: the plugin is now named TillFoundry Scheduler Watchdog and its text domain is tillfoundry-scheduler-watchdog, matching the WordPress.org directory slug. The admin menu slugs, store product slug, plugin file name and licence endpoints are unchanged, so no bookmark, setting or stored data moves.

0.1.5

• Changed: the retention settings are now visibly reconciled with Action Scheduler’s own cleaner. The Cleanup tab shows the effective retention the store is actually getting: a panel reports what Action Scheduler’s own cleaner will keep (through the action_scheduler_retention_period filter and, on Action Scheduler 4.x, action_scheduler_retention_period_for_failed) next to what Scheduler Watchdog’s own cleanup deletes. A merchant who asks to keep a year of history can now see that Action Scheduler honours it instead of losing the log at 31 days.
• Changed: on Action Scheduler 3.9.x, which does not purge failed actions itself, the panel says so instead of implying a failed-action retention period that core ignores.

0.1.4

• Changed: retention settings are reconciled with Action Scheduler’s own cleaner. A „Keep complete actions (days)“, „Keep canceled actions (days)“ or „Keep failed actions (days)“ value above Action Scheduler’s 31-day (complete/canceled) or ~90-day (failed) default is now honoured by Action Scheduler’s daily cleanup as well as by Scheduler Watchdog’s own run. Action Scheduler’s built-in default is never shortened; a shorter value still takes effect through Scheduler Watchdog’s own cleanup and its 7-day/30-day hard floors.
• Fixed: the retention filters are now inert while the master „Enable Scheduler Watchdog“ switch is off, so a disabled watchdog no longer changes Action Scheduler’s cleanup behaviour.
• Fixed: the stored licence key is masked in the Licence tab instead of being printed in the clear, and an unchanged masked field is never re-verified as if it were the key. Settings notices are escaped before they are printed.
• Release metadata: Tested up to is 6.0, the WordPress version this build is tested against.

0.1.3

• Accessibility: each queue-health card now explains itself in visible text instead of a tooltip, so a sighted touch or keyboard user can read what „Stale claims“ and the other cards mean. The text is still available to assistive technology.
• Accessibility: the dashboard, settings and event screen controls get a 44x44px minimum tap target on touch (coarse-pointer) devices, and the event screen gains the same visible focus outlines as the rest of the admin.
• The Developer tab and its two frontend switches are now shown and saved only for administrators with manage_options. A Shop Manager who can manage the plugin no longer sees them, and a save by that user leaves their stored values alone instead of resetting them.
• The Event Log and Settings submenu items now use short labels rather than repeating „Scheduler Watchdog:“ in front of each.
• When Action Scheduler is not active, the dashboard shows a short „No queue to watch yet“ empty state instead of repeating the full environment notice that already appears above it.
• The licence-expired message now says that every feature keeps working, so no action is needed. The licence status table no longer prints a „Plan“ row.
• The Verify licence control now shows its no-JavaScript instruction before the disabled button, and the licence row wraps cleanly on narrow screens.
• The dashboard stops polling for fresh numbers while its browser tab is hidden and resumes when the tab becomes visible, so a background tab no longer burns a request per interval.
• Rebuilt the distributed package so the release ZIP is byte-identical to the current source tree.

0.1.2

• Fixed: „Keep complete actions (days)“, „Keep canceled actions (days)“ and „Keep failed actions (days)“ are now applied to Action Scheduler’s own cleaner as well, so a value above Action Scheduler’s 31-day (complete/canceled) or ~90-day (failed) default is not cut short by Action Scheduler’s separate daily cleanup. Scheduler Watchdog extends Action Scheduler’s retention through its supported filters and never shortens Action Scheduler’s own default.
• Fixed: rebuilt the distributed package so the release ZIP is byte-identical to the current source tree.
• Changed: the Cleanup settings now explain which retention value wins and where the hard minimum ages apply.

0.1.1

• Fixed: „Keep complete actions (days)“, „Keep canceled actions (days)“ and „Keep failed actions (days)“ are now applied to Action Scheduler’s own cleaner as well. A value above Action Scheduler’s 31-day (complete/canceled) or ~90-day (failed) default is no longer cut short by Action Scheduler’s separate daily cleanup.
• Changed: the Cleanup settings now explain which retention value wins and where the hard minimum ages apply.
• Changed: the privacy wording is now specific. The readme makes no blanket no-personal-data claim; it states that no order, customer, refund or order-item data is stored and names the alert-recipient addresses and per-user notice state that are.

0.1.0

• Initial release.
• Queue health dashboard: pending, past-due, in-progress and failed-in-window counts, plus a WordPress dashboard widget.
• Top failing hooks, slowest hooks and largest backlogs.
• Email alerts for failed actions, stalled/past-due hooks, a missing or overdue queue runner, and stale in-progress claims, with a per-alert cooldown.
• Safe, retention-based cleanup of old complete, failed and canceled actions through Action Scheduler’s own cleaner, with hard minimum ages and a preview.
• Stale-claim recovery.
• Configurable recipients, thresholds and retention.
• HPOS compatibility declaration and multisite-aware uninstall behind an explicit opt-in.