| 开发者 | lijnam |
|---|---|
| 更新时间 | 2026年10月3日 08:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/.No. WooCommerce is not required, and the plugin declares no hard plugin dependency, so WordPress will not refuse to activate it when WooCommerce is absent. Action Scheduler is the real dependency. WooCommerce bundles Action Scheduler, so on a normal store it is already there. If you run Action Scheduler standalone, monitoring, alerting and cleanup all work too; only the WooCommerce-specific HPOS declaration and the built-in WooCommerce critical-hook presets are skipped. When Action Scheduler itself is missing, the plugin still activates but stays inert and tells you what is missing. The plugin's screens are never placed inside the WooCommerce menu: they live under the plugin's own top-level Scheduler Watchdog menu, with the dashboard, Event Log and Settings as its submenus.
Action Scheduler is the background job queue used by WooCommerce and many extensions. Every scheduled task is stored as an "action" with a hook name, a due date and a status. Scheduler Watchdog reads that queue to measure it.
No. Scheduler Watchdog is a single free plugin with every feature included: the dashboard, email alerting, the event log and safe cleanup all ship here, with no key, no account, no time limit and no capability that switches off. There is no paid tier to upgrade to, so nothing is locked and no purchase link is needed. Updates arrive through the WordPress.org plugin directory like any other free plugin, and the plugin registers no update channel of its own.
Never pending or in-progress work. Cleanup only ever removes old complete, failed and canceled actions, through Action Scheduler's own cleaner. There are hard minimum ages of 7 days for complete/canceled actions and 30 days for failed actions, regardless of what the settings say. A longer "keep" value is also applied to Action Scheduler's own cleaner — which otherwise removes complete/canceled actions after 31 days and failed actions after about 90 days on its own schedule — so raising the setting to keep a year of history is actually honoured. Cleanup is off until you enable it, and a preview button shows exactly what would be removed first.
Enable Debug logging on the Advanced tab, then open WooCommerce → Status → Logs and select the scheduler-watchdog source. Without WooCommerce, entries go to the PHP error log instead.
Yes. The metrics table is time-bucketed and pruned on a daily retention run (14 days by default), the dashboard caps the number of hooks it reads, and the shutdown fallback sampler is throttled to once a minute. On stores processing 500+ orders a day, sampling remains cheap because the hot path only writes to memory and flushes once per request.
Yes. Scheduler Watchdog does not touch order storage at all. WooCommerce → Status → Compatibility lists it as HPOS compatible.
No. This free build makes no outbound request at all: no analytics, no telemetry, no external alerting service and no licence check. A dormant licence client is bundled for a companion add-on, but this build registers no screen that accepts a key, so on a normal install it never contacts anything. See External Services below for the endpoints that client would use if a companion add-on were ever installed.
Scheduler Watchdog stores no order, customer, refund or order-item data. It records the Action Scheduler hook names, counts, durations and action IDs it needs to measure the queue. It also stores two things that can contain personal data: the alert-recipient email addresses you configure, kept in the scheduler_watchdog_settings option, and per-user notice state kept in the scheduler_watchdog_dismissed_notices and scheduler_watchdog_queued_notices user-meta keys, which remembers which plugin notices a user has dismissed or still needs to see. To remove the recipient addresses, clear the Alert recipients field in the plugin settings. The per-user notice state is removed automatically when the affected WordPress user account is deleted. Enabling Delete data on uninstall removes the plugin's settings, custom tables and transients when the plugin is deleted. Failed actions can also record the error text returned by the failing integration in the plugin's own events log.
Open the plugin's own Scheduler Watchdog menu. The version is printed next to the dashboard title and in the admin footer on every Scheduler Watchdog screen, so you never have to open Plugins → Installed Plugins to answer it.
scheduler_watchdog_features filter.index.php and a merchant whose Action Scheduler was missing never saw it where they could act on it.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.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.Tested up to is 6.0, the WordPress version this build is tested against.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.