Linux 软件免费装

ModelGain Queue Health for Action Scheduler

开发者 upaccn
更新时间 2026年10月14日 13:03
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce cron site health action scheduler scheduled actions

下载

0.1.1

详情介绍:

Action Scheduler powers background work for WooCommerce and many other WordPress plugins. When Scheduled Actions begin to fail or become past due, the built-in queue tells you what exists but can still leave the most important questions unanswered: Is the backlog abnormal? Which hook is causing most of it? Which plugin probably owns that hook? Is the default runner available? ModelGain Queue Health for Action Scheduler adds a read-only diagnostic screen under Tools → Action Scheduler Health. The first release focuses on diagnosis rather than cleanup: The dashboard uses Healthy, Review, and Critical states as troubleshooting guidance. A small transient backlog can be normal, and ownership evidence does not prove that a plugin is the root cause. The plugin does not cancel, delete, rerun, reschedule, or edit third-party actions. It makes no external API calls and does not send telemetry.

安装:

  1. Upload the plugin or install it from WordPress.org when available.
  2. Activate ModelGain Queue Health for Action Scheduler from the Plugins screen.
  3. Open Tools → Action Scheduler Health.
If no active plugin or theme has loaded Action Scheduler, the plugin will simply report that no Action Scheduler runtime was detected.

常见问题:

Does this plugin delete or repair scheduled actions?

No. Version 0.1.1 is deliberately read-only. It diagnoses the queue and gives conservative next-step guidance, but it does not mutate scheduled actions.

Is every past-due action a problem?

No. A short-lived backlog can occur during normal queue processing. The health state considers counts, age, recent failures, long-running work, and runner signals together.

How does plugin ownership detection work?

When a callback for a problematic hook is currently registered, the plugin inspects the callback source file and maps it to WordPress core, a plugin, a must-use plugin, or a theme. This is evidence about ownership, not proof that the component caused the failure.

Does the support report include order or customer data?

The report intentionally excludes Action Scheduler arguments. It contains queue counts, runner diagnostics, hook names, and likely owner information.

Does it require WooCommerce?

No. It works with any active Action Scheduler runtime, whether Action Scheduler is provided by WooCommerce or another plugin or theme.

更新日志:

0.1.1 0.1.0