Recommended for every store. Fixes a saved-but-ignored setting: the slow-hook threshold now filters the slowest-hooks table and REST response, numeric settings enforce their declared minimum on save, and the "Action Scheduler is required" notice now appears on the plugin's own screens.<\/p>","0.1.6":"
Recommended for every store. Internal rename only: the plugin is the same Scheduler Watchdog, now named TillFoundry Scheduler Watchdog with its text domain aligned to the WordPress.org directory slug. Monitoring, alerting and cleanup are unchanged and no settings migrate.<\/p>","0.1.5":"
Recommended for every store. The retention settings are now visibly reconciled with Action Scheduler's own cleaner: the Cleanup tab reports the effective retention the store is actually getting, so a longer "Keep ... (days)" value is visibly honoured instead of silently cut short.<\/p>","0.1.4":"
Recommended for every store. Retention settings now demonstrably govern Action Scheduler's own cleaner as well as Scheduler Watchdog's cleanup, and a disabled watchdog no longer changes Action Scheduler's cleanup behaviour.<\/p>","0.1.3":"
Recommended for every store. A Shop Manager who can manage the plugin no longer sees the Developer tab, the queue-health cards explain themselves in visible text, touch controls get larger tap targets, and the licence wording now makes clear that no key is required.<\/p>","0.1.2":"
Recommended for anyone who has raised a "Keep ... (days)" retention setting: older complete, canceled and failed actions are no longer deleted earlier than configured by Action Scheduler's own cleaner. Also rebuilds the package from the current source.<\/p>","0.1.1":"
Recommended for anyone who has raised a "Keep ... (days)" retention setting, so older complete, canceled or failed actions are not deleted earlier than configured by Action Scheduler's own cleaner.<\/p>","0.1.0":"
Initial release. No action needed.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3716117,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3716117,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3716117,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3716117,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3716117,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.7"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3716117,"resolution":"1","location":"assets","locale":"","width":1440,"height":1080},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3716117,"resolution":"2","location":"assets","locale":"","width":1440,"height":1080},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3716117,"resolution":"3","location":"assets","locale":"","width":1440,"height":1080},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3716117,"resolution":"4","location":"assets","locale":"","width":1440,"height":1080}},"screenshots":{"1":"The queue health dashboard: 12,480 pending actions, the failures in the last fifteen minutes, and the hooks behind both.","2":"The event log, filtered by severity, hook and date \u2014 each alert with the message that explains it.","3":"Thresholds: what counts as a runaway job, how long a hook may take, and what happens when one appears.","4":"Cleanup: the dry-run preview of what a cleanup would remove before anything is deleted."}},"plugin_section":[262246],"plugin_tags":[225911,1110,283022,5603,286],"plugin_category":[45,54],"plugin_contributors":[200752],"plugin_business_model":[],"class_list":["post-375909","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-action-scheduler","plugin_tags-alerts","plugin_tags-background-jobs","plugin_tags-monitoring","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-security-and-spam-protection","plugin_contributors-lijnam","plugin_committers-lijnam"],"banners":{"banner":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/banner-772x250.png?rev=3716117","banner_2x":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/banner-1544x500.png?rev=3716117","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/icon.svg?rev=3716117","icon":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/icon.svg?rev=3716117","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/screenshot-1.png?rev=3716117","caption":"The queue health dashboard: 12,480 pending actions, the failures in the last fifteen minutes, and the hooks behind both."},{"src":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/screenshot-2.png?rev=3716117","caption":"The event log, filtered by severity, hook and date \u2014 each alert with the message that explains it."},{"src":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/screenshot-3.png?rev=3716117","caption":"Thresholds: what counts as a runaway job, how long a hook may take, and what happens when one appears."},{"src":"https:\/\/ps.w.org\/tillfoundry-scheduler-watchdog\/assets\/screenshot-4.png?rev=3716117","caption":"Cleanup: the dry-run preview of what a cleanup would remove before anything is deleted."}],"raw_content":"\n
Every WooCommerce background job runs through Action Scheduler: marketing and CRM sync, ERP and 3PL pushes, subscription renewals, review requests, email follow-ups, importers. When one integration misbehaves it can enqueue hundreds of thousands of actions or fire them in an ever-tightening loop. PHP workers are consumed, the database is hammered, and the storefront starts returning errors.<\/p>\n\n
Scheduler Watchdog sits beside Action Scheduler and watches it continuously.<\/p>\n\n
Built for real stores<\/strong><\/p>\n\n What you get<\/strong><\/p>\n\n Scheduler Watchdog never reads or writes orders, order items, refunds or customer records. It operates only on Action Scheduler's own queue. It stores no order, customer, refund or order-item data. The personal data it does store is limited to the alert-recipient email addresses you configure in its settings, and a small per-user notice flag that remembers which of the plugin's admin notices you have dismissed or still need to see.<\/p>\n\n This free plugin contacts no external service on its own: it declares only free capabilities, every one of them works with no licence key, and a site that never enters a key makes no outbound request. The optional licence client is retained as a dormant key-validation endpoint only; no paid plan is on sale, no capability is gated behind it, and it stays dormant until you choose to enter a key. If you do enter a key, it is sent to the TillFoundry licence server at The licence endpoints are:<\/p>\n\n Each request sends the same installation record plus the licence key:<\/p>\n\n The request also carries the site URL in an If the licence server is unreachable, the plugin keeps working: monitoring, alerting and cleanup never depend on it, and a previously validated licence stays valid until the server can be reached again. No error from the licence service blocks a page or an admin action.<\/p>\n\n\n Action Scheduler must be present for the plugin to do anything. It ships inside WooCommerce, or can be installed as a standalone plugin. The plugin declares no hard plugin dependency, so WordPress never blocks its activation over a missing plugin: it activates on any WordPress site that meets the version requirements, and when Action Scheduler is absent it shows a dismissible admin notice naming Action Scheduler as required and otherwise stays inert.<\/p>\n\n\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n No paid plan is on sale. The complete plugin is free to download and use, with no licence key, no trial, no time limit and no capability that switches off. Monitoring, email alerting and safe cleanup are all included. Updates are manual downloads from this store: the plugin registers no WordPress update channel and checks for no update of its own.<\/p><\/dd>\n Never pending or in-progress work. Cleanup only ever removes old complete<\/strong>, failed<\/strong> and canceled<\/strong> 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 \u2014 which otherwise removes complete\/canceled actions after 31 days and failed actions after about 90 days on its own schedule \u2014 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.<\/p><\/dd>\n Enable Debug logging<\/strong> on the Advanced<\/strong> tab, then open WooCommerce \u2192 Status \u2192 Logs<\/strong> and select the 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.<\/p><\/dd>\n Yes. Scheduler Watchdog does not touch order storage at all. WooCommerce \u2192 Status \u2192 Compatibility lists it as HPOS compatible.<\/p><\/dd>\n Only if you enter a licence key, and then only to the licence server at 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 \n
\n
External Services<\/h3>\n\n
https:\/\/tillfoundry.com<\/code> only after you save it<\/strong>.<\/p>\n\n\n
https:\/\/tillfoundry.com\/api\/v1\/activate<\/code> \u2014 called when you save a licence key, to register this installation against the key.<\/li>\nhttps:\/\/tillfoundry.com\/api\/v1\/validate<\/code> \u2014 called when you press Verify licence now<\/strong>, and automatically in the background at most every twelve hours while a key is stored, to confirm the key is still valid.<\/li>\nhttps:\/\/tillfoundry.com\/api\/v1\/deactivate<\/code> \u2014 called when you press Deactivate this site<\/strong>, to release the activation slot.<\/li>\n<\/ul>\n\n\n
X-Site-URL<\/code> header and in the user-agent string. The service records the request IP address. See the provider's privacy policy<\/a> and terms of service<\/a>.<\/p>\n\n\n
\/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this plugin require WooCommerce?<\/h3><\/dt>\n
What is Action Scheduler?<\/h3><\/dt>\n
Is there a paid plan?<\/h3><\/dt>\n
Does the plugin delete my jobs?<\/h3><\/dt>\n
Where are the debug logs?<\/h3><\/dt>\n
scheduler-watchdog<\/code> source. Without WooCommerce, entries go to the PHP error log instead.<\/p><\/dd>\nDoes it work on a high-volume store?<\/h3><\/dt>\n
Is it HPOS compatible?<\/h3><\/dt>\n
Does the plugin send my data anywhere?<\/h3><\/dt>\n
https:\/\/tillfoundry.com<\/code> to activate or validate that key. See External Services<\/strong> below for the exact endpoints and the data sent. Nothing is sent when no key is entered. No analytics, no telemetry, no external alerting service.<\/p><\/dd>\nWhat does GDPR erasure mean for this plugin?<\/h3><\/dt>\n
scheduler_watchdog_settings<\/code> option, and per-user notice state kept in the scheduler_watchdog_dismissed_notices<\/code> and scheduler_watchdog_queued_notices<\/code> 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<\/strong> 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<\/strong> 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.<\/p><\/dd>\n\n<\/dl>\n\n\n0.1.7<\/h4>\n\n
\n
index.php<\/code> and a merchant whose Action Scheduler was missing never saw it where they could act on it.<\/li>\n0.1.6<\/h4>\n\n
\n
tillfoundry-scheduler-watchdog<\/code>, 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.<\/li>\n<\/ul>\n\n0.1.5<\/h4>\n\n
\n
action_scheduler_retention_period<\/code> filter and, on Action Scheduler 4.x, action_scheduler_retention_period_for_failed<\/code>) 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.<\/li>\n0.1.4<\/h4>\n\n
\n
Tested up to<\/code> is 6.0, the WordPress version this build is tested against.<\/li>\n<\/ul>\n\n0.1.3<\/h4>\n\n
\n
manage_options<\/code>. 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.<\/li>\n0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n