This plugin is a classical malware.

Of course, we disagree entirely.

Action Scheduler is not malware, and our team is not in the business of producing malware. We’re all deeply invested in WordPress, its community and ecosystem—and the idea we would knowingly cause harm is offensive.

In case it helps others, I’ll also just point out that there is a closely related forum thread over here, in which we’ve already addressed some of the key points raised in the current version of this review. So, rather than go through the individual points you raised here one-by-one, I’ll just make a few observations:

• Action Scheduler is a library, like many other libraries, that other pieces of software can decide to use if they feel it will help them to achieve their goals.
• Lots of plugins, including our very own WooCommerce, do just that. With 5+ million active installs to its name, that means Action Scheduler is in use on a lot of websites—and that’s just WooCommerce: many other popular WordPress plugins also include it.
• Given the above, if it was causing widespread disruption across the WordPress ecosystem, I’d expect there to be many more threads and reviews like this one than actually exist … web hosts in particular would not shy away from letting us know that it’s claiming all their resources. The reality is, it runs well and without issue for the overwhelming majority.
• Clearly, the fact it is in such widespread use suggests many plugin teams also have faith in it and understand it offers more than WP Cron can provide, else why would they use it? Certainly, they don’t decide to use it on a whim: it’s because it offers them (and therefore their users) an advantage.

By itself, Action Scheduler doesn’t really do much, and doesn’t sit there consuming all the server’s resources: if nothing is waiting to be processed, it quickly hands back control.

Action Scheduler simply offers a pipeline for getting work done. It means a plugin author can decide to defer something (sending an email, or updating some stats, or really whatever they want) so that the current request is not unduly slowed down. Of course, generally speaking, the work still needs to happen—and if too much work is deferred, or the size of the workload is excessive, then that can lead to problems.

However, that’s entirely in the control of plugin authors, and essentially the same thing is true even if Action Scheduler is taken out of the picture (stick around long enough, and you are sure to come across a case where a plugin attempts to handle intensive workloads on every single request).

All question to developers regarding this behavior return with answer like “it runs as we wish, keep enjoying slow down your site” or buy our other plugins or employ us to find why your site is slow down. Explanations about clear difference with Scheduled Actions working as they with and limited they just ignore.

I’m not sure where this is coming from or what you are referring to.

Clearly, you weren’t happy when you last interacted with us, but we also didn’t suggest you go out and buy additional plugins or propose that everything was fine in your case. Perhaps you are at least partly referring to your interactions with other teams besides our own?

What I will say though is that, on our side, we always want to hear from our users and learn how we can do better. Now, the support forums here on WordPress.org are not our preferred channel, but, as you can tell, we do still monitor them and respond.

If you want to request extra resources or documentation to help you exercise finer control over the way Action Scheduler runs, please feel free to research existing open and closed issues, or raise new ones of your own if needed.