SchedSense: Fast Diagnostics for Action Scheduler

SchedSense: Fast Diagnostics for Action Scheduler helps administrators investigate delayed or failing scheduled work. It reads Action Scheduler through its public APIs and reports queue totals, overdue pending actions, potentially stuck in-progress actions, failed actions, and relevant site health checks. Counts and source attribution are clearly identified as bounded samples where applicable.

Features

• Queue totals for pending, overdue, failed, in-progress, and completed actions.
• Overdue-age buckets from one hour to seven days, with links to matching action lists.
• Flags in-progress actions with no recorded update for over one hour as potentially stuck; long callbacks can be intentional.
• Checks WP-Cron configuration, the local WordPress loopback, and the local REST API.
• Attributes registered callbacks to likely source plugins using callback file metadata; uncertain matches are labelled.
• Bounded, filterable action lists by status, age range, exact hook, and exact group. Action arguments are never displayed.
• A confirmed, per-action delete control only for actions that are still failed. Deleting an entry does not repair or retry its callback.
• A copyable support report that excludes action arguments, credentials, cookies, customer records, and complete server paths.
• No telemetry, advertising, review nags, external account, analytics, remote service, or frontend assets.

Diagnostics run on the current WordPress site. The loopback check follows WordPress Site Health behavior: it posts a test marker to this site’s wp-cron.php, includes the site’s current login cookies and optional HTTP Basic Authentication for that same request, and honors the https_local_ssl_verify filter. The marker makes wp-cron.php finish without starting cron jobs. The REST API check also requests this site’s own REST endpoint. No diagnostic data is sent to a third-party service.

SchedSense does not bundle, replace, reset, retry, reschedule, or directly execute Action Scheduler actions. An authorized administrator can explicitly delete a selected failed action record after confirmation; the server checks that its status is still failed. Deleting a record does not fix or retry its callback. An administrator can also request WordPress’s normal cron spawner; due callbacks may then run, including callbacks that process Action Scheduler actions.